From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFA: close-on-exec internal file descriptors
Date: Sat, 06 Dec 2008 15:59:00 -0000 [thread overview]
Message-ID: <m37i6dwb1c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081206152551.GA3047@caradoc.them.org> (Daniel Jacobowitz's message of "Sat\, 6 Dec 2008 10\:25\:51 -0500")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> If you build with headers that include O_CLOEXEC support, but the
Daniel> running kernel is too old, will this fail to open entirely? Or are
Daniel> unknown open flags ignored?
I don't know, but I will find out.
Daniel> Also, WDYT about separating the goal from the mechanism? With this
Daniel> patch, every bit of gdb knows "we close file descriptors on exec";
Daniel> if it was gdb_open, it would just be "gdb-specific version of open".
Sounds good to me, I'll do this.
Tom
next prev parent reply other threads:[~2008-12-06 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 0:39 Tom Tromey
2008-12-06 8:14 ` Eli Zaretskii
2008-12-06 15:58 ` Tom Tromey
2008-12-06 16:52 ` Daniel Jacobowitz
2008-12-06 17:05 ` Eli Zaretskii
2008-12-06 16:54 ` Eli Zaretskii
2008-12-06 15:26 ` Daniel Jacobowitz
2008-12-06 15:59 ` Tom Tromey [this message]
2008-12-06 15:42 ` Mark Kettenis
2008-12-06 22:06 ` Tom Tromey
2008-12-07 19:26 ` Mark Kettenis
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=m37i6dwb1c.fsf@fleche.redhat.com \
--to=tromey@redhat.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