Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: msnyder@vmware.com
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] fork-child.c, fork_inferior: Delete ifdef'd code and unused variable.
Date: Tue, 01 Mar 2011 08:49:00 -0000	[thread overview]
Message-ID: <201103010849.p218n0je030214@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <4D6C437F.3030700@vmware.com> (message from Michael Snyder on	Mon, 28 Feb 2011 16:53:19 -0800)

> Date: Mon, 28 Feb 2011 16:53:19 -0800
> From: Michael Snyder <msnyder@vmware.com>
> 
> checked in.
> 
> 2011-02-28  Michael Snyder  <msnyder@vmware.com>
> 
> 	* fork-child.c (fork_inferior): Remove ifdef'd code and
> 	unused variable.
> 
> Index: fork-child.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/fork-child.c,v
> retrieving revision 1.61
> diff -u -p -u -p -r1.61 fork-child.c
> --- fork-child.c	11 Jan 2011 15:10:01 -0000	1.61
> +++ fork-child.c	1 Mar 2011 00:50:41 -0000
> @@ -367,12 +367,11 @@ fork_inferior (char *exec_file_arg, char
>  	  /* Otherwise, we directly exec the target program with
>  	     execvp.  */
>  	  int i;
> -	  char *errstring;
>  
>  	  execvp (exec_file, argv);
>  
>  	  /* If we get here, it's an error.  */
> -	  errstring = safe_strerror (errno);
> +	  safe_strerror (errno);

Wait a moment!  That safe_strerror() call is pretty much a no-op now.
I'm sure whoever wrote that code intended to actually display the
error string.


  reply	other threads:[~2011-03-01  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01  0:53 Michael Snyder
2011-03-01  8:49 ` Mark Kettenis [this message]
2011-03-01 18:57   ` Michael Snyder

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=201103010849.p218n0je030214@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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