From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [patch] xml-support, xml-syscall, target-description, xml-tdesc, inferior, record, gcore, jit, progspace.c unused vars.
Date: Fri, 07 May 2010 03:15:00 -0000 [thread overview]
Message-ID: <201005070015.14134.sergiodj@redhat.com> (raw)
In-Reply-To: <4BE376F5.70300@vmware.com>
On Thursday 06 May 2010 23:12:05, Michael Snyder wrote:
> Index: xml-syscall.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/xml-syscall.c,v
> retrieving revision 1.5
> diff -u -p -r1.5 xml-syscall.c
> --- xml-syscall.c 5 Apr 2010 15:58:53 -0000 1.5
> +++ xml-syscall.c 7 May 2010 02:08:49 -0000
> @@ -237,8 +237,6 @@ syscall_parse_xml (const char *document,
> struct cleanup *result_cleanup;
> struct gdb_xml_parser *parser;
> struct syscall_parsing_data data;
> - char *expanded_text;
> - int i;
>
> parser = gdb_xml_create_parser_and_cleanup (_("syscalls info"),
> syselements, &data);
This is OK for this file. Thanks.
--
Sergio
prev parent reply other threads:[~2010-05-07 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 2:12 Michael Snyder
2010-05-07 3:15 ` Sergio Durigan Junior [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=201005070015.14134.sergiodj@redhat.com \
--to=sergiodj@redhat.com \
--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