public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: gdb@sources.redhat.com, Himanshu Chandola <himanshuc@picorp.com>
Subject: Re: SIGINT not passed to process on cygwin
Date: Mon, 12 Sep 2005 14:30:00 -0000	[thread overview]
Message-ID: <20050912142957.GB10960@trixie.casa.cgf.cx> (raw)
In-Reply-To: <17189.11405.951424.968636@farnswood.snap.net.nz>

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

  parent reply	other threads:[~2005-09-12 14:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12  6:07 Himanshu Chandola
2005-09-12  7:21 ` Nick Roberts
2005-09-12  7:43   ` Himanshu Chandola
2005-09-12 10:06     ` Dave Korn
2005-09-12 14:30   ` Christopher Faylor [this message]
2005-09-12 14:35     ` Re[2]: " Konstantin Karganov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050912142957.GB10960@trixie.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=gdb@sources.redhat.com \
    --cc=himanshuc@picorp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).