Re: CGF: please review my logic Re: bash/cmd CTRL-C problem...

[Christopher Faylor <cgf@redhat.com>]

On Tue, Jan 08, 2002 at 10:00:33AM +1100, Robert Collins wrote:
>----- Original Message -----
>From: "Christopher Faylor" <cgf@redhat.com>
>> >It succeeds! (I'm running a slightly modified cygwin here, which as
>the
>> >patch at the end of this email shows (in combination with the source
>:})
>> >should always indicate if there is an error).
>>
>> It should always succeed.  A non-cygwin app should have a cygwin stub
>> associated with it.
>
>Did you read further down? I realised that... I was interested if you
>thought my hypothesis was feasible.

Not in any great detail, no.  I was addressing your apparent surprise over
the fact that getsem was able to retrieve a semaphore.

If you are looking for the "stub" code, it's in spawn_guts, around line
1078 in the current sources.

I'd suggest tracing what happens there.

cgf

>===
>So here's my best guess as to whats happening:
>When you hit CTRL-C, it propogates to
>signals.exe (handled as you expect)
>bash.exe (still attached to the console and gets handled via default
>signal handler - exit and terminate all subprocess's - which kills
>signals.exe)
>===
>
>Rob
>
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/

-- 
cgf@redhat.com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/