Wireshark-bugs: [Wireshark-bugs] [Bug 11602] NBAP dissector crashes
Date: Sat, 17 Oct 2015 17:25:27 +0000

Comment # 10 on bug 11602 from
Created attachment 13921 [details]
crash1.pcap - wireshark gui crashes after profile switch

Change 11117 successfully fixed crash3.pcap scenario. I do not experience
tshark crashes any longer.

But I still have wireshark-gtk crash. To reproduce:
1. load crash1.pcap
2. Change profile (eg. from status line) to some other.

Here goes my backtrace:
#0  0x00007f03202a435b in umts_fp_init_protocol () at packet-umts_fp.c:4499
#1  0x00007f031c187d4d in g_slist_foreach () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f031fb346cd in init_dissection () at packet.c:249
#3  0x00007f031fb28753 in epan_new () at epan.c:160
#4  0x000000000042f419 in rescan_packets (cf=0x7fe980 <cfile>, action=""
action_item=0x38 <error: Cannot access memory at address 0x38>, redissect=7) at
file.c:1838
#5  0x00000000004420ee in tb80211_add_label (text=<optimized out>, tb=0x1) at
main_80211_toolbar.c:341
#6  0x00007f031c43f245 in g_closure_invoke () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x00007f031c450f6c in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x00007f031c459778 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x00007f031c4599df in g_signal_emit () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007f031d36ca20 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x00007f031d3f8f07 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x00007f031c43f474 in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007f031c459087 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007f031c4599df in g_signal_emit () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x0000000000447333 in menu_recent_read_finished () at main_menubar.c:4260
#16 0x0000000000441e66 in copy_global_profile (profile_name=<optimized out>) at
main.c:3808
#17 change_configuration_profile (profile_name=0x2091a40 "nbap") at main.c:3825
#18 0x00007f031c158b88 in g_hash_table_lookup () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f031c450f6c in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007f031c459778 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007f031c4599df in g_signal_emit () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007f031d5eae16 in gtk_widget_activate () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#23 0x00007f031d4d9d86 in gtk_menu_shell_activate_item () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
---Type <return> to continue, or q <return> to quit---
#24 0x00007f031d4da10a in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x00007f031d4bb44e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#26 0x00007f031c43f474 in ?? () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x00007f031c458b30 in g_signal_emit_valist () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x00007f031c4599df in g_signal_emit () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x00007f031d5ebe34 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#30 0x00007f031d4b8d5e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#31 0x00007f031d4ba96e in gtk_main_do_event () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#32 0x00007f031d062b72 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#33 0x00007f031c169c5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007f031c169f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007f031c16a272 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007f031d4b9c25 in gtk_main () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#37 0x00000000004240d9 in main (argc=0, argv=0x7ffd97234e00) at main.c:2994


You are receiving this mail because:
  • You are watching all bug changes.