Re: Another sigwaitinfo problem (with testcase)

[Daniel Colascione <dancol@dancol.org>]

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

On 8/16/2012 11:43 AM, Christopher Faylor wrote:
> On Tue, Aug 14, 2012 at 10:36:39PM -0700, Daniel Colascione wrote:
>> When run on a Linux machine, this program starts up and blocks on sigwaitinfo.
>> You can suspend and resume the program using usual job control facilities, and
>> on SIGINT, the program prints a message and exits. When the program resumes
>> after being stopped, it prints "resumed".
>>
>> With the 2012-08-07 Cygwin snapshot, this program prints "resumed" immediately
>> after receiving SIGTSTP, then fails to respond to any signal, even signals not
>> in the blocked set. A simpler test program that just calls "raise (SIGSTOP)"
>> property stops itself before resuming execution.
> 
> This should be fixed in the latest snapshot.
> 
> Thanks for the test case.

Thanks for the fix. It's incomplete, though. Previously, C-z would make the
program print "resumed", then become insensitive the signals present in
waitmask. With the 2012-08-16 snapshot, C-z stops the program, but on
resumption, it doesn't print "resumed". Instead, on resumption, the program
enters the same signal-insensitive state it did with the 2012-08-07 snapshot.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]