From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: close-on-exec internal file descriptors
Date: Sat, 06 Dec 2008 17:05:00 -0000 [thread overview]
Message-ID: <E1L90Zp-0002hZ-Kr@fencepost.gnu.org> (raw)
In-Reply-To: <20081206165126.GA9117@caradoc.them.org> (message from Daniel Jacobowitz on Sat, 6 Dec 2008 11:51:26 -0500)
> Date: Sat, 6 Dec 2008 11:51:26 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> On Sat, Dec 06, 2008 at 08:58:03AM -0700, Tom Tromey wrote:
> > Eli> Can we do something more safe than this arbitrary [20] limitation?
> >
> > I don't think there is any point, because the mode argument to fopen
> > is never longer than 4 characters or so. However, if you really want
> > this, I will change it to a malloc.
>
> I find that alloca is good for these situations.
`alloca' is fine with me.
next prev parent reply other threads:[~2008-12-06 17:05 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 [this message]
2008-12-06 16:54 ` Eli Zaretskii
2008-12-06 15:26 ` Daniel Jacobowitz
2008-12-06 15:59 ` Tom Tromey
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=E1L90Zp-0002hZ-Kr@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--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