From: Himanshu Chandola <himanshuc@picorp.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: SIGINT not passed to process on cygwin
Date: Mon, 12 Sep 2005 07:43:00 -0000 [thread overview]
Message-ID: <432531B0.1000908@picorp.com> (raw)
In-Reply-To: <17189.11405.951424.968636@farnswood.snap.net.nz>
thanks that helped.
Although in cygwin ^C is set to intr, the problem continued to be the same.
The ^C on gdb didn't stop it.
Himanshu
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
>
> > Worse Ctrl + C interrupts don't
> > work on the running gdb.
> > gdb version :6.3.50_2004-12-28-cvs (cygwin-special)
>
>Assuming Cygwin has stty, if you type "stty -a" what is SIGINT (intr) bound
>to? Does it say ^C does anything? If you want it to send SIGINT type:
>
>stty intr ^C (remember to use quoted-insert (^V) before typing ^C).
>
>Nick
>
>
>
next prev parent reply other threads:[~2005-09-12 7:43 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 [this message]
2005-09-12 10:06 ` Dave Korn
2005-09-12 14:30 ` Christopher Faylor
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=432531B0.1000908@picorp.com \
--to=himanshuc@picorp.com \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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).