From: David Carlton <carlton@math.stanford.edu>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <ac131313@redhat.com>
Subject: [rfa] missing frame_register
Date: Mon, 17 Mar 2003 19:47:00 -0000 [thread overview]
Message-ID: <ro11y15g4he.fsf@jackfruit.Stanford.EDU> (raw)
There's a remaining use of get_saved_register in
gdbtk/generic/gdbtk-register.c. This patch attempts to convert it
over, but I might have gotten it wrong: I just copied some similar
conversions from Andrew's earlier patch. All I've done is verified
that this patch allows the file in question to compile; I don't use
gdbtk or run the gdbtk tests, so I don't have any way of checking
whether or not it works.
Andrew, is this OK? I assume it's either obviously okay to commit or
obviously wrong.
David Carlton
carlton@math.stanford.edu
2003-03-17 David Carlton <carlton@math.stanford.edu>
* generic/gdbtk-register.c (get_register): Replace use of
get_saved_register by frame_register.
Index: gdbtk-register.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/generic/gdbtk-register.c,v
retrieving revision 1.15
diff -u -p -r1.15 gdbtk-register.c
--- gdbtk-register.c 12 Feb 2003 00:39:46 -0000 1.15
+++ gdbtk-register.c 17 Mar 2003 19:43:25 -0000
@@ -287,8 +287,11 @@ get_register (int regnum, void *arg)
return;
}
- get_saved_register (raw_buffer, &optim, (CORE_ADDR *) NULL, deprecated_selected_frame,
- regnum, (enum lval_type *) NULL);
+ {
+ int realnum;
+ frame_register (deprecated_selected_frame, regnum, &optim,
+ NULL, NULL, &realnum, raw_buffer);
+ }
if (optim)
{
Tcl_ListObjAppendElement (NULL, result_ptr->obj_ptr,
next reply other threads:[~2003-03-17 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 19:47 David Carlton [this message]
2003-03-17 20:56 ` Keith Seitz
2003-03-17 21:05 ` David Carlton
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=ro11y15g4he.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.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