From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [commit] fork-child.c, fork_inferior: Delete ifdef'd code and unused variable.
Date: Tue, 01 Mar 2011 00:53:00 -0000 [thread overview]
Message-ID: <4D6C437F.3030700@vmware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 13 bytes --]
checked in.
[-- Attachment #2: unused14.txt --]
[-- Type: text/plain, Size: 1112 bytes --]
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);
fprintf_unfiltered (gdb_stderr, "Cannot exec %s ", exec_file);
i = 1;
@@ -384,10 +383,6 @@ fork_inferior (char *exec_file_arg, char
i++;
}
fprintf_unfiltered (gdb_stderr, ".\n");
-#if 0
- /* This extra info seems to be useless. */
- fprintf_unfiltered (gdb_stderr, "Got error %s.\n", errstring);
-#endif
gdb_flush (gdb_stderr);
_exit (0177);
}
next reply other threads:[~2011-03-01 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 0:53 Michael Snyder [this message]
2011-03-01 8:49 ` Mark Kettenis
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=4D6C437F.3030700@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
/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