Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [patch] Zap more #ifdef HAVE_VFORK
Date: Fri, 06 Apr 2001 11:47:00 -0000	[thread overview]
Message-ID: <3ACE0F3C.A0A184B2@cygnus.com> (raw)
In-Reply-To: <1010327002437.ZM2540@ocotillo.lan>

Kevin Buettner wrote:
> 
> On Mar 26, 11:45am, Andrew Cagney wrote:
> 
> > Missed this when re-fixing the autoconfed vfork() call.
> [...]
> >     /* Clone the debugger. */
> > - #ifdef HAVE_VFORK
> >     if (debug_fork)
> >       debugger_pid = fork ();
> >     else
> >       debugger_pid = vfork ();
> > - #else
> > -   debugger_pid = fork ();
> > - #endif
> 
> This didn't make any sense to me at first.  It did when I went back
> and (re)read

I know it doesn't make sense :-)  It is how autoconf does it though :-/

> If we're going to use the AC_FUNC_VFORK mechanisms, might I suggest
> that we do one of the following?
> 
>     1) Document the fact that the autoconf cleverness *might* actually
>        have defined vfork to be fork at each use vfork.

Ok by me.  In general adding comments explaining how bits of code work
are probably obvious fixes.

>     2) Create a gdb_fork() which does the appropriate thing *and*
>        documents the autoconf cleverness in the guts of gdb_fork().

I don't think this one would work very well.  From memory you're not
ment to return from a vfork().

	Andrew


  reply	other threads:[~2001-04-06 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26  8:45 Andrew Cagney
2001-03-26 16:24 ` Kevin Buettner
2001-04-06 11:47   ` Andrew Cagney [this message]
2001-04-06 12:14     ` Kevin Buettner

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=3ACE0F3C.A0A184B2@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=kevinb@cygnus.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