From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [patch] ser-pipe.c (pipe_open): Ignore SIGINTs in child.
Date: Tue, 27 Apr 2010 03:52:00 -0000 [thread overview]
Message-ID: <20100427035220.0C02F84C2B@ruffy.mtv.corp.google.com> (raw)
I was debugging "tar rem | ..." today and found that typing ^c
killed the child of the pipe.
I will check this in in a few days if there are no objections.
2010-04-26 Doug Evans <dje@google.com>
* ser-pipe.c (pipe_open): Ignore SIGINTs in child.
Index: ser-pipe.c
===================================================================
RCS file: /cvs/src/src/gdb/ser-pipe.c,v
retrieving revision 1.24
diff -u -p -r1.24 ser-pipe.c
--- ser-pipe.c 20 Apr 2010 05:52:07 -0000 1.24
+++ ser-pipe.c 27 Apr 2010 03:49:05 -0000
@@ -98,6 +98,8 @@ pipe_open (struct serial *scb, const cha
/* Child. */
if (pid == 0)
{
+ signal (SIGINT, SIG_IGN);
+
/* re-wire pdes[1] to stdin/stdout */
close (pdes[0]);
if (pdes[1] != STDOUT_FILENO)
next reply other threads:[~2010-04-27 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 3:52 Doug Evans [this message]
2010-04-27 17:44 ` Tom Tromey
2010-04-27 17:57 ` Doug Evans
2010-04-27 20:27 ` Tom Tromey
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=20100427035220.0C02F84C2B@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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).