Description of problem: nfs analysis Version-Release number of selected component: wireshark-gnome-1.8.3-2.fc18 Additional info: libreport version: 2.0.17 abrt_version: 2.0.17 backtrace_rating: 4 cmdline: wireshark tcpdump_hanging.pcap crash_function: __strlen_sse2_pminub kernel: 3.6.3-3.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 __strlen_sse2_pminub at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38 : #1 construct_match_selected_string at proto.c:6906 : #2 proto_can_match_selected at proto.c:7130 : #3 set_menus_for_selected_tree_row at main_menubar.c:5425 : #4 tree_view_selection_changed_cb at main.c:829 : #5 _g_closure_invoke_va at gclosure.c:840 : #8 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1604 : #9 gtk_tree_view_real_set_cursor at gtktreeview.c:13208 : #10 gtk_tree_view_row_deleted at gtktreeview.c:9120 : #15 gtk_tree_model_row_deleted at gtktreemodel.c:1868
Created attachment 635053 [details] File: core_backtrace
Created attachment 635054 [details] File: environ
Created attachment 635055 [details] File: limits
Created attachment 635056 [details] File: backtrace
Created attachment 635057 [details] File: cgroup
Created attachment 635058 [details] File: smolt_data
Created attachment 635059 [details] File: executable
Created attachment 635060 [details] File: maps
Created attachment 635061 [details] File: dso_list
Created attachment 635062 [details] File: build_ids
Created attachment 635063 [details] File: proc_pid_status
Created attachment 635064 [details] File: var_log_messages
Created attachment 635065 [details] File: open_fds
Michele, do you have stepsand a capture to reproduce this? I think the problem is similar to one that a user of my GlusterFS dissector mentioned: - https://github.com/nixpanic/gluster-wireshark-1.4/issues/21 At the moment, I think the GTK3 implementation is to blame. With a gtk2 version of the package I can not reproduce the issue anymore. Care to test that out? GTK2 packages are available from here: - http://repos.fedorapeople.org/repos/devos/wireshark-gluster/fedora-18/x86_64/
Hi Niels ;) nope I don't really have exact steps to reproduce yet. I will spend some more time into digging the exact issue. It seems to happen when I work with bigger dumps but haven't pinpointed it yet. I also think this is gtk3 related. I will try some patches that I saw flowing upstream. Let's see if I get lucky cheers, Michele
I am unable to reproduce the crash that was reported to me (see comment #14) with the svn version of wireshark from 20121114. The RPMs (wireshark-1.8.3-2.fc18.0.svn20121114) are also available from my fedora-18 repository (http://repos.fedorapeople.org/repos/devos/wireshark-gluster/fedora-18/x86_64/). I think it is likely that this issue has been fixed in upstream wireshark.
Please, try wireshark-1.8.4-1.fc18, which is available in koji, soon in repositories.
Created attachment 656518 [details] "bt f" from a crashed wireshark-1.8.4-1.fc18.x86_64 Sorry, wireshark-1.8.4-1.fc18 from koji does not fix this. Download the .pcap from https://github.com/nixpanic/gluster-wireshark-1.4/issues/21 1. wireshark /root/glusterfs-dissector-crash.pcap 2. Click on Packet No. 4 (V2 GETSPEC Call) and expand "GlusterFS Handshake" treeview in the payload pane. 3. Click on Packet No. 5 and wireshark will segfault. (It may be that the GlusterFS protocols are not detected correctly, disabling the incorrectly used dissectors may be required, see https://github.com/nixpanic/gluster-wireshark-1.4/wiki/Disable-non-Gluster-protocols-in-Wireshark)
Was looking at fields in a SMB capture. backtrace_rating: 4 Package: wireshark-gnome-1.8.4-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
While examining packet capture available at http://media.packetlife.net/media/blog/attachments/424/TCP_example.cap I clicked packet number 37 and wireshare crashed instantly. backtrace_rating: 4 Package: wireshark-gnome-1.8.4-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
I was just capturing over my wireless interface. I had one virtualbox instance working with bride adapter and disable it. backtrace_rating: 4 Package: wireshark-gnome-1.8.5-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
Clicked on packet containing a TLS message backtrace_rating: 4 Package: wireshark-gnome-1.8.5-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
I was analyzing SSL network traffic. backtrace_rating: 4 Package: wireshark-gnome-1.8.5-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
The crash was caused by broken gtk2 vs. gtk3 calls. Wireshark was reverted back to use gtk2 as a gui library. This one can't be reproduced anymore, closing.