From: Daniel Jacobowitz <drow@false.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix a glitch in debugging 32-bit process with 64-bit GDB.
Date: Tue, 09 Dec 2008 02:08:00 -0000 [thread overview]
Message-ID: <20081209020744.GA11173@caradoc.them.org> (raw)
In-Reply-To: <20081209013252.9E1C83A6B2E@localhost>
On Mon, Dec 08, 2008 at 05:32:52PM -0800, Paul Pluzhnikov wrote:
> The problem is that in findvar.c:
>
> case LOC_ARG:
> if (frame == NULL)
> return 0;
> addr = get_frame_args_address (frame);
> if (!addr)
> return 0;
> addr += SYMBOL_VALUE (var);
> break;
>
> What happens if sizeof(addr) == 8 (64-bit gdb), len == 4 (32-bit target),
> get_frame_args_address() returns 0xffffbf98 (typical stack address)
> and SYMBOL_VALUE() returns -16?
>
> We end up with an impossible target address of 0x1ffffbf88.
Conclusion doesn't follow from example, but I think I'm just
confused... Do you mean that SYMBOL_VALUE is -16U or -16UL, and
that's where the wrapping comes from? But SYMBOL_VALUE is a long,
signed. Is SYMBOL_VALUE (long) 0xfffffff0? If that's the case then
the debug reader might be to blame.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-12-09 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 1:33 Paul Pluzhnikov
2008-12-09 2:08 ` Daniel Jacobowitz [this message]
2008-12-09 2:43 ` Paul Pluzhnikov
2008-12-09 11:30 ` Peter Schauer
2008-12-09 13:34 ` Daniel Jacobowitz
2008-12-10 11:14 ` Joel Brobecker
2008-12-10 15:59 ` Paul Pluzhnikov
2008-12-10 23:21 ` Paul Pluzhnikov
2008-12-11 8:57 ` Andreas Schwab
[not found] ` <8ac60eac0812111601v20566268h6f7977c71e5b8a8f@mail.gmail.com>
2008-12-12 0:11 ` Paul Pluzhnikov
2008-12-13 16:02 ` Joel Brobecker
2008-12-13 18:18 ` Paul Pluzhnikov
2008-12-15 8:59 ` Joel Brobecker
2008-12-15 21:47 ` Paul Pluzhnikov
2008-12-16 4:48 ` Joel Brobecker
2008-12-11 9:21 ` 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=20081209020744.GA11173@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.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