From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com, fnasser@redhat.com
Subject: Re: [RFA] Use vfork in shell_escape
Date: Tue, 05 Nov 2002 13:43:00 -0000 [thread overview]
Message-ID: <20021105214414.GB17994@nevyn.them.org> (raw)
In-Reply-To: <20021022015205.GA22323@nevyn.them.org>
On Mon, Oct 21, 2002 at 09:52:05PM -0400, 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?
Updated as suggested, to use gdb_vfork.h. Fernando, is this OK?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2002-11-05 Daniel Jacobowitz <drow@mvista.com>
* Makefile.in (cli-cmds.o): Add $(gdb_vfork_h).
* cli/cli-cmds.c: Include "gdb_vfork.h".
(shell_escape): Use vfork.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.274
diff -u -p -r1.274 Makefile.in
--- Makefile.in 2 Nov 2002 15:13:34 -0000 1.274
+++ Makefile.in 5 Nov 2002 21:40:52 -0000
@@ -2311,7 +2311,7 @@ cli-cmds.o: $(srcdir)/cli/cli-cmds.c $(d
$(gdb_wait_h) $(gdb_regex_h) $(gdb_string_h) $(filenames_h) \
$(ui_out_h) $(top_h) $(cli_decode_h) $(cli_script_h) \
$(cli_setshow_h) $(cli_cmds_h) $(source_h) $(linespec_h) \
- $(expression_h) $(language_h) $(objfiles_h)
+ $(expression_h) $(language_h) $(objfiles_h) $(gdb_vfork_h)
$(CC) -c $(INTERNAL_CFLAGS) $(srcdir)/cli/cli-cmds.c
cli-decode.o: $(srcdir)/cli/cli-decode.c $(defs_h) $(symtab_h) \
$(gdb_regex_h) $(gdb_string_h) $(ui_out_h) $(cli_cmds_h) \
Index: cli/cli-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/cli/cli-cmds.c,v
retrieving revision 1.22
diff -u -p -r1.22 cli-cmds.c
--- cli/cli-cmds.c 22 Sep 2002 22:18:41 -0000 1.22
+++ cli/cli-cmds.c 5 Nov 2002 21:40:53 -0000
@@ -25,6 +25,7 @@
#include "gdb_wait.h" /* For shell escape implementation */
#include "gdb_regex.h" /* Used by apropos_command */
#include "gdb_string.h"
+#include "gdb_vfork.h"
#include "linespec.h"
#include "expression.h"
#include "language.h"
@@ -517,7 +518,7 @@ shell_escape (char *arg, int from_tty)
else
p++; /* Get past '/' */
- if ((pid = fork ()) == 0)
+ if ((pid = vfork ()) == 0)
{
if (!arg)
execl (user_shell, p, 0);
next prev parent reply other threads:[~2002-11-05 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
2002-10-22 14:59 ` Elena Zannoni
2002-11-05 13:43 ` Daniel Jacobowitz [this message]
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=20021105214414.GB17994@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@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