From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [ob] remote.c, eliminate unused variables
Date: Wed, 05 May 2010 20:51:00 -0000 [thread overview]
Message-ID: <201005052151.19745.pedro@codesourcery.com> (raw)
In-Reply-To: <4BE1D93F.8000309@vmware.com>
On Wednesday 05 May 2010 21:46:55, Michael Snyder wrote:
> 2010-05-05 Michael Snyder <msnyder@vmware.com>
>
> * remote.c (remote_threads_info): Delete unused variable.
> (process_stop_reply): Delete unused variable.
> (remote_get_trace_status): Delete unused variables.
>
> Index: remote.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/remote.c,v
> retrieving revision 1.405
> diff -u -p -r1.405 remote.c
> --- remote.c 5 May 2010 15:05:57 -0000 1.405
> +++ remote.c 5 May 2010 20:43:46 -0000
> @@ -2512,8 +2512,8 @@ remote_threads_info (struct target_ops *
> {
> struct gdb_xml_parser *parser;
> struct threads_parsing_context context;
> - struct cleanup *back_to = make_cleanup (null_cleanup, NULL);
>
> + make_cleanup (null_cleanup, NULL);
Are you making sure (in all your patches) that the reason the
variables are unused isn't itself a bug? In this case, creating a
null_cleanup and not storing a pointer anywhere is
highly suspicious...
--
Pedro Alves
next prev parent reply other threads:[~2010-05-05 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 20:47 Michael Snyder
2010-05-05 20:51 ` Pedro Alves [this message]
2010-05-05 21:14 ` Michael Snyder
2010-05-05 21:41 ` Pedro Alves
2010-05-05 22:22 ` Michael Snyder
2010-05-05 22:39 ` Pedro Alves
2010-05-07 17:42 ` Tom Tromey
2010-05-07 18:51 ` 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=201005052151.19745.pedro@codesourcery.com \
--to=pedro@codesourcery.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