public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/23763] Runtime.getRuntime().exec() signalling
Date: Wed, 26 Oct 2005 09:01:00 -0000 [thread overview]
Message-ID: <20051026090106.13546.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23763-216@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from tromey at gcc dot gnu dot org 2005-10-26 09:01 -------
Sorry for the delay on this.
The patch looks reasonable enough to me. It needs a small
amount of reformatting and a ChangeLog entry.
Also I think the call to signal() is not needed, a custom
handler is reset to the default on exec.
--
tromey at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2005-10-26 09:01:06
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23763
next prev parent reply other threads:[~2005-10-26 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23763-216@http.gcc.gnu.org/bugzilla/>
2005-10-26 8:48 ` aeby at graeff dot com
2005-10-26 9:01 ` tromey at gcc dot gnu dot org [this message]
2005-10-26 18:05 ` aeby at graeff dot com
2005-11-08 19:44 ` tromey at gcc dot gnu dot org
2005-11-08 20:59 ` tromey at gcc dot gnu dot org
2005-11-08 21:00 ` tromey at gcc dot gnu dot org
2005-11-08 21:01 ` tromey at gcc dot gnu dot org
2005-09-07 13:14 [Bug libgcj/23763] New: " aeby at graeff dot com
2005-09-07 13:17 ` [Bug libgcj/23763] " aeby at graeff dot com
2005-09-07 13:18 ` aeby at graeff dot com
2005-09-08 8:51 ` aeby at graeff dot com
2005-09-10 2:21 ` pinskia at gcc dot gnu dot org
2005-09-15 14:27 ` aeby at graeff dot com
2005-09-15 14:27 ` aeby at graeff dot com
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=20051026090106.13546.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).