Re: [Wireshark-dev] Building with libtool /epan
Yep, but i dont have a version checked out by SVN. I dl the source code.. so i have directly a Makefile.in On Tue, 04 Oct 2011 09:24:17 -0400, Jeff Morriss jeff.morriss...@gmail.com wrote: Marcel Haas wrote: Hmm Nope.. the makefile will work without any error but at libwireshark.la libdir= is no entry and i guess thats the library so i can not use my functions and now i havent an entry at the .deps file folder I changed it like it was before what i have done is at Makefile.common LIBWIRESHARK_SRC = ... list_mh.c \ ... LIBWIRESHARK_INCLUDES = ... list_mh.c \ ... and Makefile.in Normally you should not edit Makefile.in: it is generated (from the .am and .common files) when you run ./autogen.sh . ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Building with libtool /epan
Thx Jeff .. it works..im happy :) I run ./autogen ./configure and make and it finally works Thx a lot buddy u made my day ;) On Tue, 04 Oct 2011 09:24:17 -0400, Jeff Morriss jeff.morriss...@gmail.com wrote: Marcel Haas wrote: Hmm Nope.. the makefile will work without any error but at libwireshark.la libdir= is no entry and i guess thats the library so i can not use my functions and now i havent an entry at the .deps file folder I changed it like it was before what i have done is at Makefile.common LIBWIRESHARK_SRC = ... list_mh.c \ ... LIBWIRESHARK_INCLUDES = ... list_mh.c \ ... and Makefile.in Normally you should not edit Makefile.in: it is generated (from the .am and .common files) when you run ./autogen.sh . ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
(gdb) bt #0 0x00316b8482a0 in g_markup_escape_text () from /lib64/libglib-2.0.so.0 #1 0x004629b6 in welcome_filename_link_new (menu_item=0x1a04d30, label=read_sleb128: Corrupted DWARF expression. ) at main_welcome.c:626 #2 main_welcome_add_recent_capture_file (widget_cf_name=0x185e900 /home/ykaul/wireshark/\212\340\001, menu_item=0x1a04d30) at main_welcome.c:706 #3 0x004550c4 in add_recent_items (merge_id=5, ui_manager=0x17abb20) at main_menubar.c:3927 #4 0x004575a4 in add_menu_recent_capture_file (cf_name=optimized out) at main_menubar.c:4122 #5 0x0047c575 in read_set_recent_pair_dynamic (key=optimized out, value=0x1a00f50 \212\340\001, private_data=optimized out, return_range_errors=optimized out) at recent.c:740 #6 0x75732a96 in read_prefs_file (pf_path=0x880b80 /home/ykaul/.wireshark/recent_common, pf=0x1a05800, pref_set_pair_fct=0x47c500 read_set_recent_pair_dynamic, private_data=0x0) at prefs.c:1531 #7 0x0047e12e in recent_read_dynamic (rf_path_return=0x7fffe078, rf_errno_return=0x7fffe0b4) at recent.c:945 #8 0x0042d7e4 in main (argc=0, argv=0x7fffe1e0) at main.c:2875 It worked before the massive updates of last night (which I'm not sure unrelated). It's a bit more difficult to dissect in SVN, so hopefully someone has a clue what went wrong. Y. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
Kaul wrote: (gdb) bt #0 0x00316b8482a0 in g_markup_escape_text () from /lib64/libglib-2.0.so.0 #1 0x004629b6 in welcome_filename_link_new (menu_item=0x1a04d30, label=read_sleb128: Corrupted DWARF expression. ) at main_welcome.c:626 #2 main_welcome_add_recent_capture_file (widget_cf_name=0x185e900 /home/ykaul/wireshark/\212\340\001, menu_item=0x1a04d30) at main_welcome.c:706 #3 0x004550c4 in add_recent_items (merge_id=5, ui_manager=0x17abb20) at main_menubar.c:3927 #4 0x004575a4 in add_menu_recent_capture_file (cf_name=optimized out) at main_menubar.c:4122 #5 0x0047c575 in read_set_recent_pair_dynamic (key=optimized out, value=0x1a00f50 \212\340\001, private_data=optimized out, return_range_errors=optimized out) at recent.c:740 #6 0x75732a96 in read_prefs_file (pf_path=0x880b80 /home/ykaul/.wireshark/recent_common, pf=0x1a05800, pref_set_pair_fct=0x47c500 read_set_recent_pair_dynamic, private_data=0x0) at prefs.c:1531 #7 0x0047e12e in recent_read_dynamic (rf_path_return=0x7fffe078, rf_errno_return=0x7fffe0b4) at recent.c:945 #8 0x0042d7e4 in main (argc=0, argv=0x7fffe1e0) at main.c:2875 It worked before the massive updates of last night (which I'm not sure unrelated). It's a bit more difficult to dissect in SVN, so hopefully someone has a clue what went wrong. Not sure if this is related: I had a core dump last night while *writing* the recent file. A make clean/all fixed it. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
On 10/5/2011 4:57 AM, Kaul wrote: It worked before the massive updates of last night (which I'm not sure unrelated). It's a bit more difficult to dissect in SVN, so hopefully someone has a clue what went wrong. Y. Wireshark (SVN #39269) works OK on my Windows and Fedora 32-bit systems. Are you still having problems ?? ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Replace TRUE/FALSE with proper ENC_* in proto_tree_add_item() using a script.
Bill Meier wmeier@... writes: In this case, given the specifics, I found it fairly simple to do what I needed in Perl. Should these functions be modified to take an encoding argument instead of a little_endian argument, then the Perl script run on them as well to convert TRUE/FALSE to ENC_LITTLE_ENDIAN/ENC_BIG_ENDIAN? tvb_fake_unicode() tvb_get_ephemeral_faked_unicode() proto_tree_add_bitmask() proto_tree_add_bitmask_text() proto_item_add_bitmask_tree() = static in epan/proto.c only - Chris ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Replace TRUE/FALSE with proper ENC_* in proto_tree_add_item() using a script.
Chris Maynard skrev 2011-10-05 20:36: Bill Meierwmeier@... writes: In this case, given the specifics, I found it fairly simple to do what I needed in Perl. Should these functions be modified to take an encoding argument instead of a little_endian argument, then the Perl script run on them as well to convert TRUE/FALSE to ENC_LITTLE_ENDIAN/ENC_BIG_ENDIAN? tvb_fake_unicode() tvb_get_ephemeral_faked_unicode() proto_tree_add_bitmask() proto_tree_add_bitmask_text() proto_item_add_bitmask_tree()= static in epan/proto.c only - Chris proto_tree_add_bits_item() proto_tree_add_bits_item_ret_val() should also have the FALSE value changed - Anders ___ Sent via:Wireshark-dev mailing listwireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
On Wed, Oct 5, 2011 at 4:25 PM, Bill Meier wme...@newsguy.com wrote: On 10/5/2011 4:57 AM, Kaul wrote: It worked before the massive updates of last night (which I'm not sure unrelated). It's a bit more difficult to dissect in SVN, so hopefully someone has a clue what went wrong. Y. Wireshark (SVN #39269) works OK on my Windows and Fedora 32-bit systems. Are you still having problems ?? Yes, I do. 'svn update' followed by 'make clean ; make distclean ; my config script ; make' did not help. This morning I was on Fedora 15/64b, now on Fedora16beta/64b. I'm on #39276. Something tells me that until I delete the prefs., it's not going to go away :( Y. __**__** ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives: http://www.wireshark.org/**lists/wireshark-devhttp://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/**options/wireshark-devhttps://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request@**wireshark.orgwireshark-dev-requ...@wireshark.org ?subject=**unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] core dump on starting wireshark (latest SVN update 39266?)
On Wed, Oct 05, 2011 at 10:07:36PM +0200, Kaul wrote: I'm on #39276. Something tells me that until I delete the prefs., it's not going to go away :( Do a mv ~/.wireshark/preferences ~/.wireshark/preferences.old and see if it works fine after that. If so, sharing your preferences.old file with us may allow us to repliate the problem. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Can g_warning() be removed from gtk/main_menubar.c
Can the calls to g_warning() be removed from gtk/main_menubar.c? I noticed it when I go to View - Time Display Format - Millseconds when it was on Automatic before. There are more cases of the g_warning(), which were presumably for testing when the UI manager code was being created. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Recursive Heuristic Dissectors calls
I have a custom protocol that uses a well know TCP port and a such have connected a heuristic dissector to tcp. My dissector works fine if there is only my custom protocol in the packet, but I have run into a case where the first part of the packet has several groups of my protocol, but at the end is a normal h248 chunk of data. How should I handle this? I would like for the TCP dissector to try a heuristic dissector look up after each chuck of custom data. After a quick look at the TCP dissector, it appears that dissector_try_heuristic, defined in epan/proto.c, is called only once per packet. Any ideas? Thanks as always. Alex Lindberg ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Can g_warning() be removed from gtk/main_menubar.c
Stephen Fisher skrev 2011-10-06 00:09: Can the calls to g_warning() be removed from gtk/main_menubar.c? I noticed it when I go to View - Time Display Format - Millseconds when it was on Automatic before. There are more cases of the g_warning(), which were presumably for testing when the UI manager code was being created. I removed the unconditional ones in revision 39289, should the rest be moved inside #if DEBUG or removed? Regards Anders ___ Sent via:Wireshark-dev mailing listwireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
