From: "Andrew Burgess" <aburgess@broadcom.com>
To: insight@sourceware.org
Subject: [OBV PATCH] Move comment back into correct place.
Date: Thu, 05 Sep 2013 13:20:00 -0000 [thread overview]
Message-ID: <52288492.6010001@broadcom.com> (raw)
The comment for the variable old_regs in gdbtk-register.c had come
unstuck. I've moved it back into place.
Hope this is ok to commit as obvious.
thanks,
Andrew
2013-09-05 Andrew Burgess <aburgess@broadcom.com>
* generic/gdbk-register.c (old_regs): Move the comment about this
variable next to the definition.
Index: ./gdb/gdbtk/generic/gdbtk-register.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-register.c,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -p -r1.47 -r1.48
--- ./gdb/gdbtk/generic/gdbtk-register.c 15 Jul 2013 07:42:21 -0000 1.47
+++ ./gdb/gdbtk/generic/gdbtk-register.c 5 Sep 2013 13:14:28 -0000 1.48
@@ -43,11 +43,6 @@ typedef union
/* Type of our mapping functions */
typedef void (*map_func)(int, map_arg);
-/* This contains the previous values of the registers, since the last call to
- gdb_changed_register_list.
-
- It is an array of (NUM_REGS+NUM_PSEUDO_REGS)*MAX_REGISTER_RAW_SIZE bytes. */
-
static int gdb_register_info (ClientData, Tcl_Interp *, int, Tcl_Obj **);
static void get_register (int, map_arg);
static void get_register_name (int, map_arg);
@@ -62,6 +57,11 @@ static int gdb_reggrouplist (ClientData,
static void get_register_types (int regnum, map_arg);
+/* This contains the previous values of the registers, since the last call to
+ gdb_changed_register_list.
+
+ It is an array of (NUM_REGS+NUM_PSEUDO_REGS)*MAX_REGISTER_RAW_SIZE bytes. */
+
static char *old_regs = NULL;
static int *regformat = (int *)NULL;
static struct type **regtype = (struct type **)NULL;
reply other threads:[~2013-09-05 13:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52288492.6010001@broadcom.com \
--to=aburgess@broadcom.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).