Wireshark-bugs: [Wireshark-bugs] [Bug 8715] New: CRASH when close Statistics => Summary windows
Bug ID |
8715
|
Summary |
CRASH when close Statistics => Summary windows after close capture
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.8.7
|
Hardware |
All
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Wireshark
|
Assignee |
bugzilla-admin@wireshark.org
|
Reporter |
alexis.lagoutte@gmail.com
|
Build Information:
--
Hi,
Working on (technical) proposals from GSOC students (for Qtshark projet), i
found a (stupid) crash.
To reproduce this crash, it is easy
1) Open a file
2) Launch Summary (Statistics => Summary)
3) Close file (File => Close)
4) Apply in Summary windows
5) Crash
The gdb output
Program received signal SIGSEGV, Segmentation fault.
wtap_write_shb_comment (wth=0x0, comment=comment@entry=0x1eeec60 "")
at wtap.c:125
125 g_free(wth->shb_hdr.opt_comment);
the backstrace :
#0 wtap_write_shb_comment (wth=0x0, comment=comment@entry=0x1eeec60 "")
at wtap.c:125
#1 0x0000000000436bb9 in cf_update_capture_comment (cf=0x823940 <cfile>,
comment=0x1eeec60 "") at file.c:3861
#2 0x00000000004737e2 in summary_ok_cb (w=<optimized out>,
view=<optimized out>) at summary_dlg.c:157
#3 0x00007ffff201d8e7 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007ffff20362df in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007ffff2036f92 in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007ffff2f189ee in ?? ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#7 0x00007ffff2fc0929 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#8 0x00007ffff201d620 in g_closure_invoke ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007ffff202eaf8 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff2036996 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007ffff2036f92 in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff30d9d9e in ?? ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x00007ffff2fbed56 in gtk_propagate_event ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#14 0x00007ffff2fbf00b in gtk_main_do_event ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#15 0x00007ffff2c33ccc in ?? ()
from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#16 0x00007ffff1b55f05 in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff1b56248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff1b566ba in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff2fbdfe7 in gtk_main ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x0000000000421d25 in main (argc=0, argv=0x7fffffffe1b0) at main.c:3190
the crash is reproduced in 1.8.x/1.10.x/trunk
A solution for fix the crash is set Summary dialog windows modal but there is a
better fix... (and this issue it is may be in other dialog windows... (Add/Edit
comment ?)
You are receiving this mail because:
- You are watching all bug changes.