Wireshark-bugs: [Wireshark-bugs] [Bug 1419] dumpcap keeps running after Wireshark crashes
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
ulf.lamping@xxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Critical |Major
------- Comment #3 from ulf.lamping@xxxxxx 2007-05-16 20:18 GMT -------
Well, if dumpcap is called from Wireshark, the special command line parameter
'Z' is used to get it into "Wireshark slave" mode (capture_child flag in the
sources) - e.g. supressing some printf output and using a pipe to WS instead.
So yes, dumpcap knows it's in this mode.
I've tried some bugfixes, which did not fix this bug :-(
dumpcap sends some status message through the sync_pipe to Wireshark after some
packets rushed in. If Wireshark was closed, writing to the sync_pipe should
result in an error - but on Win32 it doesn't do so :-(
Reading the signal_pipe which is used to stop the capture on Win32, also
doesn't return an error when the other side of the pipe exists - so I really
don't have a good idea what to do here :-(
So I don't have a good idea to fix this bug ...
I've changed this bug from critical to major - while it can be quite annoying,
I can't see why this should be critical ...
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
