Re: SIGINT not passed to process on cygwin

Christopher Faylor
2005-09-12T14:30:06Z

On Mon, Sep 12, 2005 at 07:21:49PM +1200, Nick Roberts wrote:
>Himanshu Chandola writes:
>>Has anyone encountered the following:
>>attach gdb on cygwin to a running process. Send SIGINT to the process.
>>gdb handles SIGINT and stops. Try to continue the running process , the
>>SIGINT is not passed to the process.
>
>By default, GDB doesn't pass SIGINT to the process:
>
>(gdb) info signal 2
>Signal Stop Print Pass to program Description
>SIGINT Yes Yes No Interrupt
>
>If you want it to do so, type:
>
>(gdb) handle 2 pass

Right. That's what I do when I want the signal to be propagate.

I don't know if this is what is happening but, unfortunately, gdb only
understands windows signals. Physically pressing CTRL-C is an event
which gdb will recognize as a "SIGINT". Sending the process a SIGINT
via "kill" or some other method will not be recognized by gdb.

cgf