From: Andrew Cagney <ac131313@redhat.com>
To: Michael Snyder <msnyder@redhat.com>, fnasser@redhat.com
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Use vfork in shell_escape
Date: Tue, 22 Oct 2002 14:43:00 -0000 [thread overview]
Message-ID: <3DB5C67E.9040700@redhat.com> (raw)
In-Reply-To: <3DB5BC72.3DE58BD@redhat.com>
> Daniel Jacobowitz wrote:
>
>>
>> On Tue, Oct 22, 2002 at 01:54:01PM -0700, Michael Snyder wrote:
>
>> > Daniel Jacobowitz wrote:
>
>> > >
>> > > This patch is pretty obvious. I couldn't figure out why my machine was
>> > > running out of memory; forking GDB to run an 'ls' during the maint.exp tests
>> > > can be a bit heavy, since it may have all of glibc's debug info loaded.
>> > > This patch seems logical to me... OK to commit?
>
>> >
>> > Not as is. There's some auto-confery involved, since many systems
>> > (some systems?) don't have vfork. Grep for vfork in fork-child.c.
>
>>
>> Not as much as there used to be. But you're right, I goofed. OK with
>> the addition of '#include "gdb_vfork.h"', which is all fork-child.c
>> uses now?
>
>
> For all I know, that's OK -- but I don't know.
> I'll step back now, and wait for someone who does.
Yep, from the ARI:
HAVE VFORK #ifdef HAVE_VFORK is redundant. Include "gdb_vfork.h" and
call vfork() unconditionally.
Fernando - CLI?
Andrew
next prev parent reply other threads:[~2002-10-22 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 18:51 Daniel Jacobowitz
2002-10-22 13:54 ` Michael Snyder
2002-10-22 13:56 ` Daniel Jacobowitz
2002-10-22 14:00 ` Michael Snyder
2002-10-22 14:43 ` Andrew Cagney [this message]
2002-10-22 14:59 ` Elena Zannoni
2002-11-05 13:43 ` Daniel Jacobowitz
2003-06-21 18:39 ` Daniel Jacobowitz
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=3DB5C67E.9040700@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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