Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Stephan Springl <springl-gdb@bfw-online.de>
Cc: gdb-patches@sourceware.org
Subject: Re: fix comment typo
Date: Thu, 07 Sep 2006 16:24:00 -0000	[thread overview]
Message-ID: <20060907162415.GC1811@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0609071425100.22397@lar.bfw.de>


> while digging into the fact that gdb 6.5 does not close .gdbinit and the 
> child programs binary in the child process before execing, I found a typo.

Thanks Stephan, I committed your patch as obvious. For anything less
obvious we would need a copyright assignment in place, but this is
definitely fine.

2006-09-07  Joel Brobecker  <brobecker@adacore.com>

        From Stephan Springl  <springl-gdb@bfw-online.de>
        * fork-child.c (fork_inferior): Fix typo.

> index 8940151..44049dc 100644
> --- a/gdb/fork-child.c
> +++ b/gdb/fork-child.c
> @@ -277,7 +277,7 @@ #endif
>      (*pre_trace_fun) ();
> 
>    /* Create the child process.  Since the child process is going to
> -     exec(3) shortlty afterwards, try to reduce the overhead by
> +     exec(3) shortly afterwards, try to reduce the overhead by
>       calling vfork(2).  However, if PRE_TRACE_FUN is non-null, it's
>       likely that this optimization won't work since there's too much
>       work to do between the vfork(2) and the exec(3).  This is known


-- 
Joel


      parent reply	other threads:[~2006-09-07 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 12:30 Stephan Springl
2006-09-07 12:35 ` Andreas Schwab
2006-09-07 16:24 ` Joel Brobecker [this message]

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=20060907162415.GC1811@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=springl-gdb@bfw-online.de \
    /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