From: Keith Seitz <keiths@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: insight@sourceware.org
Subject: Re: Build insight cvs-head get error
Date: Tue, 26 Jan 2010 02:09:00 -0000 [thread overview]
Message-ID: <4B5DF87F.8010303@redhat.com> (raw)
In-Reply-To: <daef60381001250021o6b9612e0x464cd56cac549f1f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
On 01/25/2010 12:21 AM, Hui Zhu wrote:
> ../../src/gdb/gdbtk/generic/gdbtk-cmds.c: In function 'gdb_set_inferior_args':
> ../../src/gdb/gdbtk/generic/gdbtk-cmds.c:867: error: void value not
> ignored as it ought to be
I've checked in the attached patch for this.
Keith
ChangeLog
2010-01-25 Keith Seitz <keiths@redhat.com>
* generic/gdbtk-cmds.c (gdb_set_inferior_args): set_inferior_args
now works as expected. Do not strdup/free the argument string.
[-- Attachment #2: set_inferior_args.patch --]
[-- Type: text/plain, Size: 753 bytes --]
Index: generic/gdbtk-cmds.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-cmds.c,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -p -r1.114 -r1.115
--- generic/gdbtk-cmds.c 4 Jan 2010 20:14:46 -0000 1.114
+++ generic/gdbtk-cmds.c 25 Jan 2010 19:59:29 -0000 1.115
@@ -859,13 +859,7 @@ gdb_set_inferior_args (ClientData client
}
args = Tcl_GetStringFromObj (objv[1], NULL);
-
- /* The xstrdup/xfree stuff is so that we maintain a coherent picture
- for gdb. I would expect the accessors to do this, but they
- don't. */
- args = xstrdup (args);
- args = set_inferior_args (args);
- xfree (args);
+ set_inferior_args (args);
return TCL_OK;
}
next prev parent reply other threads:[~2010-01-25 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 20:01 Hui Zhu
2010-01-26 2:09 ` Keith Seitz [this message]
2010-02-02 13:56 ` Hui Zhu
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=4B5DF87F.8010303@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=teawater@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).