From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Pedro Alves <pedro@codesourcery.com>
Subject: [RFA] remote.c, clean-up mix-up
Date: Wed, 05 May 2010 22:37:00 -0000 [thread overview]
Message-ID: <4BE1F306.8060006@vmware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
I'm not sure if this clean-up ever happens, because the declaration
merely shadows an outer declaration of the same name, and the
do_cleanups call happens outside the scope of this declaration.
This is my **GUESS** as to what might be intended here.
If anybody has an alternate hypothesis, it's probably
better than mine.
[-- Attachment #2: remote2.txt --]
[-- Type: text/plain, Size: 868 bytes --]
2010-05-05 Michael Snyder <msnyder@vmware.com>
* remote.c (remote_threads_info): Remove shadowing declaration.
Index: remote.c
===================================================================
RCS file: /cvs/src/src/gdb/remote.c,v
retrieving revision 1.407
diff -u -p -5 -r1.407 remote.c
--- remote.c 5 May 2010 22:27:15 -0000 1.407
+++ remote.c 5 May 2010 22:31:28 -0000
@@ -2510,12 +2510,12 @@ remote_threads_info (struct target_ops *
struct cleanup *back_to = make_cleanup (xfree, xml);
if (xml && *xml)
{
struct gdb_xml_parser *parser;
struct threads_parsing_context context;
- struct cleanup back_to = make_cleanup (null_cleanup, NULL);
+ back_to = make_cleanup (null_cleanup, NULL);
context.items = 0;
parser = gdb_xml_create_parser_and_cleanup (_("threads"),
threads_elements,
&context);
next reply other threads:[~2010-05-05 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 22:37 Michael Snyder [this message]
2010-05-05 23:08 ` Pedro Alves
2010-05-05 23:44 ` Pedro Alves
2010-05-06 0:18 ` Pedro Alves
2010-05-06 0:28 ` 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=4BE1F306.8060006@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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