From: "Martin M. Hunt" <hunt@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] read_reg() patch
Date: Mon, 26 Jul 2004 20:57:00 -0000 [thread overview]
Message-ID: <1090875453.3021.2.camel@dragon> (raw)
In-Reply-To: <200407212036.i6LKaE0V009860@copland.kettenis.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
> I also think that the code itself is pretty unreadable. There are too
> many nested function calls. I think it could be improved by using a
> (temporary) local variable to store the result of
> extract_unsigned_integer().
How's this?
2004-07-26 Martin Hunt <hunt@redhat.com>
* dwarf2-frame.c (read_reg): Add a call to
store_unsigned_integer.
[-- Attachment #2: read_reg.patch --]
[-- Type: text/x-patch, Size: 1039 bytes --]
Index: dwarf2-frame.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2-frame.c,v
retrieving revision 1.38
diff -u -p -r1.38 dwarf2-frame.c
--- dwarf2-frame.c 23 Jul 2004 22:05:20 -0000 1.38
+++ dwarf2-frame.c 26 Jul 2004 20:54:39 -0000
@@ -209,11 +209,20 @@ read_reg (void *baton, int reg)
struct gdbarch *gdbarch = get_frame_arch (next_frame);
int regnum;
char *buf;
+ CORE_ADDR tmp;
regnum = DWARF2_REG_TO_REGNUM (reg);
buf = (char *) alloca (register_size (gdbarch, regnum));
frame_unwind_register (next_frame, regnum, buf);
+
+ /* This extracts the least significant register_size() bits and
+ extends it to the size of a pointer. Without this, big-endian
+ targets where pointer size != register size breaks. */
+ tmp = extract_unsigned_integer (buf, register_size (gdbarch, regnum));
+ store_unsigned_integer (buf, TYPE_LENGTH (builtin_type_void_data_ptr),
+ tmp);
+
return extract_typed_address (buf, builtin_type_void_data_ptr);
}
next prev parent reply other threads:[~2004-07-26 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 19:17 Martin M. Hunt
2004-07-21 20:36 ` Mark Kettenis
2004-07-26 20:57 ` Martin M. Hunt [this message]
2004-07-29 22:48 ` Mark Kettenis
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=1090875453.3021.2.camel@dragon \
--to=hunt@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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