Jakub/Wireshark-team Dopa is nothing but rename of wireshark script means at the place of ./Wireshark we run as ./dopa . So I think there is no any problem with dopa. Can you give me any other debugging idea to resolve it. Right now I am using Wireshark-1.6.2 version.
Thanks in advanced. Thanks Chandan ~~~~~~~ ============================================================================ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, July 19, 2012 12:30 AM To: [email protected] Subject: Wireshark-dev Digest, Vol 74, Issue 32 Send Wireshark-dev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://wireshark.org/mailman/listinfo/wireshark-dev or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Wireshark-dev digest..." Today's Topics: 1. tcap.tid display filter not applied as byte string (Arjan Van Der Oest) 2. Wireshark-bug (Kumar, Chandan (Chandan)) 3. Re: Wireshark-bug (Jakub Zawadzki) 4. Re: tcap.tid display filter not applied as byte string (Christopher Maynard) ---------------------------------------------------------------------- Message: 1 Date: Wed, 18 Jul 2012 12:23:38 +0200 From: Arjan Van Der Oest <[email protected]> To: Developer support list for Wireshark <[email protected]> Subject: [Wireshark-dev] tcap.tid display filter not applied as byte string Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi, When using the TCAP dissector and clicking right on a TID value (i.e.: 0c0013c0) , selecting "Apply as Filter > Selected" the display filter will be composed as "tcap.tid == 0c0013c0" and WS will error on me with "tcap.tid == 0c0013c0" isn't a valid display filter: "0c0013c0" is not a valid byte string. When manually changing the display filter to "tcap.tid == 0c:00:13:c0 the problem is solved. It seems to me the 'Apply as filter...' command from the context menu is not behaving correctly. Arjan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.wireshark.org/lists/wireshark-dev/attachments/20120718/2bbb4d44/attachment.html> ------------------------------ Message: 2 Date: Wed, 18 Jul 2012 17:37:50 +0530 From: "Kumar, Chandan (Chandan)" <[email protected]> To: "[email protected]" <[email protected]> Subject: [Wireshark-dev] Wireshark-bug Message-ID: <edcb4994b292fb4192dfca11d511adb026eda...@inbansxchmbsb1.in.alcatel-lucent.com> Content-Type: text/plain; charset="us-ascii" Hi All, Can anyone help me to resolve the following issue? When do I run Wireshark on Linux machine compilation goes fine but after opening the GUI with any pcap file, background I am getting these error messages? So what I have to do to remove these issue. (dopa:20255): Gtk-CRITICAL **: gtk_menu_attach_to_widget: assertion `GTK_IS_MENU (menu)' failed (dopa:4159): Gtk-CRITICAL **: gtk_tree_model_iter_n_children: assertion `GTK_IS_TREE_MODEL (tree_model)' failed (dopa:6369): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed (dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed (dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed Thanks Chandan ~~~~~~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.wireshark.org/lists/wireshark-dev/attachments/20120718/f913ce19/attachment.html> ------------------------------ Message: 3 Date: Wed, 18 Jul 2012 15:31:16 +0200 From: Jakub Zawadzki <[email protected]> To: Developer support list for Wireshark <[email protected]> Subject: Re: [Wireshark-dev] Wireshark-bug Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii Hi, On Wed, Jul 18, 2012 at 05:37:50PM +0530, Kumar, Chandan (Chandan) wrote: > Can anyone help me to resolve the following issue? > When do I run Wireshark on Linux machine compilation goes fine but after > opening the GUI with any pcap file, background I am getting these error > messages? > So what I have to do to remove these issue. > > (dopa:20255): Gtk-CRITICAL **: gtk_menu_attach_to_widget: assertion > `GTK_IS_MENU (menu)' failed > > (dopa:4159): Gtk-CRITICAL **: gtk_tree_model_iter_n_children: assertion > `GTK_IS_TREE_MODEL (tree_model)' failed > > (dopa:6369): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion > `GTK_IS_MENU_SHELL (menu_shell)' failed > > (dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET > (widget)' failed > > (dopa:6369): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET > (widget)' failed Erm, these errors are from some 'dopa' program, not wireshark. If you have any issues with *wireshark* please post output of wireshark --version ------------------------------ Message: 4 Date: Wed, 18 Jul 2012 14:28:55 +0000 (UTC) From: Christopher Maynard <[email protected]> To: [email protected] Subject: Re: [Wireshark-dev] tcap.tid display filter not applied as byte string Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 Arjan Van Der Oest <Arjan@...> writes: > When using the TCAP dissector and clicking right on a TID value (i.e.: 0c0013c0) , selecting "Apply as Filter > Selected" the display filter will be composed as "tcap.tid == 0c0013c0" and WS will error on me with "tcap.tid == 0c0013c0" isn't a valid display filter: "0c0013c0" is not a valid byte string. > > When manually changing the display filter to ?"tcap.tid == 0c:00:13:c0 the problem is solved. It seems to me the 'Apply as filter...' command from the context menu is not behaving correctly. Please file a bug report and include a small capture file for testing. - Chris ------------------------------ _______________________________________________ Wireshark-dev mailing list [email protected] https://wireshark.org/mailman/listinfo/wireshark-dev End of Wireshark-dev Digest, Vol 74, Issue 32 *********************************************
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
