Wireshark-bugs: [Wireshark-bugs] [Bug 2767] tshark-1.0.2 (dumpcap) signal abort core saved

From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 3 Aug 2008 04:33:59 -0700 (PDT)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2767


Moheed Moheed Ahmad <moheedm@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #2100|                            |review_for_checkin?
               Flag|                            |




--- Comment #1 from Moheed Moheed Ahmad <moheedm@xxxxxxxxx>  2008-08-03 04:33:58 PDT ---
Created an attachment (id=2100)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2100)
dumpcap.c and the diff, a windows zipped file

This Fix may not be a proper one, but tested and works.

It don't investigate route cause of problem, simply puts a hack
to avoid call to capture_loop_stop_signal_handler (signo=10) in cases
capture stop signal (ie capture_cleanup (signum=2)) has been served already

ie
Fix is based on the message 
"(process:30239): CaptureChild-INFO (recursed): Signal: Stop capture"
and stack trace.

And Finally fix is
Putting a new flag, whether Capture_stop signal has been served
or not, so that once capture_cleanup() has been called, this flag will
be set to TRUE, and the next call to capture_loop_stop_signal_handler
(signo=10)
(which inturns checks this flag and skips capture_loop_stop)won't be in effect.


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