From: Eli Zaretskii <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@false.org>
Cc: cagney@gnu.org, Ulrich.Weigand@de.ibm.com,gdb@sources.redhat.com
Subject: Re: getpid after vfork broken in recent glibc
Date: Tue, 09 Mar 2004 06:36:00 -0000 [thread overview]
Message-ID: <ud67msey0.fsf@elta.co.il> (raw)
In-Reply-To: <20040309025255.GA11922@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 8 Mar 2004 21:52:55 -0500)
> Date: Mon, 8 Mar 2004 21:52:55 -0500
> From: Daniel Jacobowitz <drow@false.org>
> >
> > We might as well simply always use fork -- the "performance" benefit is
> > hardly valid any more (Hmm, perhaps something related to this is why
> > vfork never worked, and hence was disabled, on HP/UX).
>
> Since I went to some trouble to make "shell escape" use vfork when
> possible (2003-06-21), I have to disagree with your assumption. When
> GDB is using a good-sized chunk of the RAM on a system, forking
> unnecessarily is a real pain.
>
> Given the idiotic definition of vfork, though, I guess we don't have a
> choice.
How about if glibc did us a small favor and invalidated its cached
PID on a vfork?
next prev parent reply other threads:[~2004-03-09 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 19:17 Ulrich Weigand
2004-03-09 2:41 ` Andrew Cagney
2004-03-09 2:53 ` Daniel Jacobowitz
2004-03-09 6:36 ` Eli Zaretskii [this message]
2004-03-09 13:14 ` Andreas Schwab
2004-03-09 18:53 Ulrich Weigand
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=ud67msey0.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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