Wireshark-bugs: [Wireshark-bugs] [Bug 2767] tshark-1.0.2 (dumpcap) signal abort core saved
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 13 Sep 2009 10:55:33 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2767


Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeff.morriss.ws@xxxxxxxxx
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #6 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>  2009-09-13 10:55:31 PDT ---
(In reply to comment #3)
> Created an attachment (id=3414)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3414) [details]
> possible minimal patch
> 
> dumpcap at some cases receives SIGUSR1 while still processing SIGINT. This seem
> to be bad combination as both signal handlers call g_log(). Possible solution
> is to block SIGUSR1 till we are processing SIGINT..

Thanks for the pointer.  I checked in a different fix in rev 29881:
  1) use SIGINT (instead of SIGUSR1) to tell dumpcap to exit
  2) (and) don't call g_log in the signal handler: it's not Async-Signal-Safe
after all

I added this fix to the queues for 1.0.9 and 1.2.2 as well.


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