From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: The ari hits
Date: Fri, 28 Feb 2003 01:52:00 -0000 [thread overview]
Message-ID: <20030228015238.GA17237@nevyn.them.org> (raw)
In-Reply-To: <3E5E8CAA.1080304@redhat.com>
On Thu, Feb 27, 2003 at 05:09:46PM -0500, Andrew Cagney wrote:
> Daniel,
>
> The files you recently committed trip the ARI. Can you please check
> this out.
>
> Andrew
>
> http://sources.redhat.com/gdb/current/ari/
Thanks for reminding me; this patch fixes them. Almost obvious except
for a bit that I want your opinion on - the hint on the ARI
says to use register_size but I'm not convinced that's right. Is
gdbarch_register_size always big enough that I don't need to use
gdbarch_register_raw_size?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-02-27 Daniel Jacobowitz <drow@mvista.com>
* dwarf2expr.c (new_dwarf_expr_context): Add (void) to definition.
* dwarf2loc.c (dwarf_expr_read_reg): Rename regnum argument to
dwarf_regnum. Use gdbarch_register_raw_size.
Index: dwarf2expr.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2expr.c,v
retrieving revision 1.1
diff -u -p -r1.1 dwarf2expr.c
--- dwarf2expr.c 21 Feb 2003 15:24:17 -0000 1.1
+++ dwarf2expr.c 28 Feb 2003 01:48:13 -0000
@@ -35,7 +35,7 @@ static void execute_stack_op (struct dwa
/* Create a new context for the expression evaluator. */
struct dwarf_expr_context *
-new_dwarf_expr_context ()
+new_dwarf_expr_context (void)
{
struct dwarf_expr_context *retval;
retval = xcalloc (1, sizeof (struct dwarf_expr_context));
Index: dwarf2loc.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2loc.c,v
retrieving revision 1.1
diff -u -p -r1.1 dwarf2loc.c
--- dwarf2loc.c 21 Feb 2003 15:24:17 -0000 1.1
+++ dwarf2loc.c 28 Feb 2003 01:48:13 -0000
@@ -51,17 +51,21 @@ struct dwarf_expr_baton
type will be returned in LVALP, and for lval_memory the register
save address will be returned in ADDRP. */
static CORE_ADDR
-dwarf_expr_read_reg (void *baton, int regnum, enum lval_type *lvalp,
+dwarf_expr_read_reg (void *baton, int dwarf_regnum, enum lval_type *lvalp,
CORE_ADDR *addrp)
{
- CORE_ADDR result;
struct dwarf_expr_baton *debaton = (struct dwarf_expr_baton *) baton;
- char *buf = (char *) alloca (MAX_REGISTER_RAW_SIZE);
- int optimized, realnum;
+ CORE_ADDR result;
+ char *buf;
+ int optimized, regnum, realnum, regsize;
+
+ regnum = DWARF2_REG_TO_REGNUM (dwarf_regnum);
+ regsize = gdbarch_register_raw_size (current_gdbarch, regnum);
+ buf = (char *) alloca (regsize);
- frame_register (debaton->frame, DWARF2_REG_TO_REGNUM (regnum),
- &optimized, lvalp, addrp, &realnum, buf);
- result = extract_address (buf, REGISTER_RAW_SIZE (regnum));
+ frame_register (debaton->frame, regnum, &optimized, lvalp, addrp, &realnum,
+ buf);
+ result = extract_address (buf, regsize);
return result;
}
next prev parent reply other threads:[~2003-02-28 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:07 Andrew Cagney
2003-02-28 1:52 ` Daniel Jacobowitz [this message]
2003-02-28 17:54 ` Andrew Cagney
2003-02-28 17:59 ` Daniel Jacobowitz
2003-03-02 2:01 ` Andrew Cagney
2003-03-02 3:14 ` Daniel Jacobowitz
2003-03-03 21:49 ` Daniel Jacobowitz
2003-10-10 2:52 The ARI hits Andrew Cagney
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=20030228015238.GA17237@nevyn.them.org \
--to=drow@mvista.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