From: Simon Marchi <simon.marchi@polymtl.ca>
To: Bill Morgan <arthurwilliammorgan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: win32-arm-low.c regptr 96 bits stored in 32 bit variable
Date: Sun, 28 Oct 2018 16:47:00 -0000 [thread overview]
Message-ID: <c7affefd2ba4e71ec0a69a3fc352461a@polymtl.ca> (raw)
In-Reply-To: <CAM4wpo8KAB4ff0F9+XwWkRyT_3uT6NPUQThbuM9z0fSxW8CyWw@mail.gmail.com>
On 2018-10-26 18:40, Bill Morgan wrote:
> Should this static variable ULONG zero be at least 96 bits?
>
> static char *
> regptr (CONTEXT* c, int r)
> {
> if (mappings[r] < 0)
> {
> static ULONG zero;
> /* Always force value to zero, in case the user tried to write
> to this register before. */
> zero = 0;
> return (char *) &zero;
> }
> else
> return (char *) c + mappings[r];
> }
>
> reg-arm.dat shows 96 bits for the ones that have mappings[r] == -1
>
> name:arm
> xmlarch:arm
> expedite:r11,sp,pc
> 32:r0
> 32:r1
> 32:r2
> 32:r3
> 32:r4
> 32:r5
> 32:r6
> 32:r7
> 32:r8
> 32:r9
> 32:r10
> 32:r11
> 32:r12
> 32:sp
> 32:lr
> 32:pc
> 96:f0
> 96:f1
> 96:f2
> 96:f3
> 96:f4
> 96:f5
> 96:f6
> 96:f7
> 32:fps
> 32:cpsr
Hi Bill,
By inspection, it does seem like a mistake, and that we would need to
return a pointer to a buffer at least as big as register r. But I have
no idea how to build/run/test gdbserver on win32/arm. If you are able
to confirm that there is a problem and test a fix, could you please
provide a patch?
To avoid this kind of problem again, we could return a pointer to a
dynamically-sized buffer adjusted to the size of the register.
Something like this:
static char *
regptr (CONTEXT* c, struct regcache *regcache, int r)
{
if (mappings[r] < 0)
{
static gdb::byte_vector zero;
/* Always force value to zero, in case the user tried to write
to this register before. */
zero.assign (regcache_register_size (regcache, r), 0);
return (char *) zero.data ();
}
else
return (char *) c + mappings[r];
}
Simon
next prev parent reply other threads:[~2018-10-28 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 22:41 Bill Morgan
2018-10-28 16:47 ` Simon Marchi [this message]
2018-10-29 13:50 ` Richard Earnshaw (lists)
2018-10-29 15:31 ` Simon Marchi
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=c7affefd2ba4e71ec0a69a3fc352461a@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=arthurwilliammorgan@gmail.com \
--cc=gdb@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