Comment # 12
on bug 7278
from Evan Huus
(In reply to comment #11)
> Wireshark crashed after I selected one of longest saved filters and pressed
> Start.
>
> Program received signal SIGSEGV, Segmentation fault.
> magazine_chain_pop_head (magazine_chunks=0x80299e18) at gslice.c:532
> 532 (*magazine_chunks)->data = ""
> (gdb) bt
> #0 magazine_chain_pop_head (magazine_chunks=0x80299e18) at gslice.c:532
> #1 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=1) at
> gslice.c:835
> #2 g_slice_alloc (mem_size=mem_size@entry=12) at gslice.c:994
> #3 0xb4796da1 in g_list_prepend (list=list@entry=0x80ee1240,
> data="" at glist.c:279
> #4 0xb4ad1869 in find_common_ancestor (win2=<optimized out>,
> win1=<optimized out>) at gdkwindow.c:9875
> #5 _gdk_synthesize_crossing_events (display=display@entry=0x802b50b0,
> src="" dest=dest@entry=0x80f70638,
> mode=mode@entry=GDK_CROSSING_NORMAL,
> toplevel_x=263, toplevel_y=291, mask=GDK_MOD2_MASK, time_=time_@entry=0,
> event_in_queue=event_in_queue@entry=0x0, serial=serial@entry=41556,
> non_linear=non_linear@entry=0) at gdkwindow.c:10103
> #6 0xb4ad1f28 in do_synthesize_crossing_event (data="" at
> gdkwindow.c:10411
> #7 0xb4aa7350 in gdk_threads_dispatch (data="" at
> gdk.c:512
> #8 0xb4797d11 in g_idle_dispatch (source=source@entry=0x80fe9c78,
> callback=0xb4aa72f0 <gdk_threads_dispatch>, user_data=0x80fdc6a0) at
> gmain.c:5205
> #9 0xb479b0f6 in g_main_dispatch (context=0x802bf118,
> context@entry=0x802f00d0) at gmain.c:3054
> #10 g_main_context_dispatch (context=context@entry=0x802bf118) at
> gmain.c:3630
> #11 0xb479b4a8 in g_main_context_iterate (context=0x802bf118,
> block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at
> gmain.c:3701
> #12 0xb479b923 in g_main_loop_run (loop=loop@entry=0x803f2fc0) at
> gmain.c:3895
> #13 0xb4c92a30 in IA__gtk_main () at gtkmain.c:1257
> #14 0x80029a35 in main (argc=1, argv=0xbffff014) at main.c:3193
That looks like a GTK or glib bug to me - there's no real Wireshark code in the
stack trace except for main. It could be memory corruption though...
You are receiving this mail because:
- You are watching all bug changes.