Cygwin 32bit vs 64bit difference: SIGQUIT

[Charles Wilson]

On 7/31/2013 10:11 AM, Corinna Vinschen wrote:
> On Jul 31 09:08, Charles Wilson wrote:
>> FAIL: t/tap-signal.tap 5 - TAP driver catch test termination by
>> signal SIGQUIT
>
> Hmm.
>
>    $ cat
>
> In another shell:
>
>    $ ps
> 	PID    PPID    PGID     WINPID   TTY     UID    STIME COMMAND
> 	568    2276     568       2952  pty0    11001 16:08:59 /usr/bin/tcsh
>         1696    1012    1696       1652  pty1    11001 16:09:08 /usr/bin/ps
>         1012    1112    1012       2704  pty1    11001 16:09:05 /usr/bin/tcsh
>    I    2324     568    2324        816  pty0    11001 16:09:02 /usr/bin/cat
>         1112       1    1112       1112  ?       11001 16:09:05 /usr/bin/mintty
>         2276       1    2276       2276  ?       11001 16:08:59 /usr/bin/mintty
>    $ kill -QUIT 2324
>
> In the first shell:
>
>    Quit (core dumped)
>    $
>
>> .... which doesn't really tell you much without the rest of the test
>> driver machinery, but I include it for completeness.
>>
>> The point of this post is the following question: is there a known
>> difference in the signal handling code between cygwin32 and cygwin64
>> that could explain why I see different behavior with respect to
>> SIGQUIT?
>
> No.  STC?

I'll try to extract one from the test suite, but I don't think I'll hold 
up a release waiting for the resolution (and it may be a while before I 
can construct the STC; getting ready for some travel soon...)

--
Chuck



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple