From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [ob] remote.c, eliminate unused variables
Date: Wed, 05 May 2010 20:47:00 -0000 [thread overview]
Message-ID: <4BE1D93F.8000309@vmware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: tmp10.txt --]
[-- Type: text/plain, Size: 1386 bytes --]
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);
context.items = 0;
parser = gdb_xml_create_parser_and_cleanup (_("threads"),
threads_elements,
@@ -5079,7 +5079,6 @@ process_stop_reply (struct stop_reply *s
struct target_waitstatus *status)
{
ptid_t ptid;
- struct thread_info *info;
*status = stop_reply->ws;
ptid = stop_reply->ptid;
@@ -9637,8 +9636,7 @@ remote_trace_start (void)
static int
remote_get_trace_status (struct trace_status *ts)
{
- char *p, *p1, *p_temp;
- ULONGEST val;
+ char *p;
/* FIXME we need to get register block size some other way */
extern int trace_regblock_size;
trace_regblock_size = get_remote_arch_state ()->sizeof_g_packet;
next reply other threads:[~2010-05-05 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 20:47 Michael Snyder [this message]
2010-05-05 20:51 ` Pedro Alves
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=4BE1D93F.8000309@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