From: Joel Brobecker <brobecker@adacore.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix a glitch in debugging 32-bit process with 64-bit GDB.
Date: Sat, 13 Dec 2008 16:02:00 -0000 [thread overview]
Message-ID: <20081213160110.GF6866@adacore.com> (raw)
In-Reply-To: <8ac60eac0812111603r68ffa49exd7cb0ce403d07310@mail.gmail.com>
> So, the choices appear to be:
>
> - leave GDB broken and wait for newer glibc :(
I'm just realizing that this might be a very very visible problem,
if most offsets are negative. Is that the case?
> - do sign extension, but only for N_LSYM and N_PSYM symbols as
> a heuristic.
It seems to me that this should work without negative effect
(we have to be a little careful because there is a 64bit stabs
extension on Tru64). After all, values for these types of symbols
are always offsets to some location inside a frame, and I can't see
a frame being that big.
> - pre-scan the objfile to determine highest link address, and
> do sign extension if that address is (well) below 0x80000000
Seems too much work, IMO.
--
Joel
next prev parent reply other threads:[~2008-12-13 16:02 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
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 [this message]
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=20081213160110.GF6866@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=schwab@suse.de \
/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