Wireshark-bugs: [Wireshark-bugs] [Bug 7318] assertion failed when I quit wireshark without stopp
Date: Fri, 8 Jun 2012 16:01:58 -0700 (PDT)

--- Comment #15 from Jakub Zawadzki <[email protected]> 2012-06-08 16:01:58 PDT ---
(In reply to comment #11)
> The problem is definitely that capture_input_closed() is not being called, but
> I find it odd that you're not seeing it. Nowhere in my test path do we yield
> back to the main loop, so I don't know how it's getting called when you run the
> same case?
> I've played around adding calls to capture_input_closed() in some potential few
> places, but I haven't found anything that doesn't break some other code path.
> It may be best to simply set a flag, yield back to the main loop, and let
> sync_pipe_input_cb() actually exit?

(sorry, I don't have wireshark compiled with -g)

(gdb) bt
#0  0x000000000043e6e6 in capture_input_closed ()
#1  0x000000000043b806 in sync_pipe_input_cb ()
#2  0x000000000045817d in pipe_input_cb ()
#3  0x00007f8bf90454ad in g_main_context_dispatch () from
#4  0x00007f8bf9045df0 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f8bf9045f9f in g_main_context_iteration () from
#6  0x00007f8bfa7c2ea1 in gtk_main_iteration () from
#7  0x0000000000458b6f in main_window_update ()
#8  0x000000000045d490 in main_cf_callback ()
#9  0x0000000000441a03 in cf_callback_invoke ()
#10 0x000000000044647d in cf_close ()
#11 0x00000000004f2276 in do_file_close ()

Maybe we should call by hand (in some place):
  g_main_context_iteration(NULL, FALSE)
and not rely on luck that gtk will do some window refreshing?

It might also be some glib/gtk related bug, so for references I'm using:

Anyway for me this bug has really *low* priority, so I never really read whole
capture logic.

Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.