public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "corinna at vinschen dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/18027] dwarf2 debug info after rebasing DLLs unusable
Date: Mon, 13 Feb 2023 19:48:17 +0000 [thread overview]
Message-ID: <bug-18027-4717-n0s6mmI4Gy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18027-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18027
--- Comment #10 from Corinna Vinschen <corinna at vinschen dot de> ---
(In reply to Tom Tromey from comment #8)
> > I'm pretty sure the problem is that the dwarf2 debug info contains
> > absolute addresses which don't match the load address of the DLL after
> > rebase.
>
> Ok... so if I'm understanding correctly, this might not completely
> be a gdb bug, since what's happening is that the DLL is rebased but
> some addresses in the DWARF are not updated.
Indeed, this is not necessarily a GDB bug. Apologies, but 8 years ago
it very much looked like a combined ld/GDB problem, that's why I created
https://sourceware.org/bugzilla/show_bug.cgi?id=18025 and this bug here
at the same time.
In fact, the first question is probably if the dwarf2 info couldn't
by imagebase-relative, rather than absolute. If that's possible
(and maybe even already handled in GDB?) this could be done by tweaking
the linker.
If that's not possible because of how the dwarf info is defined...
> However, maybe gdb could work around this some way, if we had a
> way to determine the original base? Like, for DWARF symbols,
> gdb could do ADDR - ORIG + NEW to compute the address?
...then it would be great if GDB could workaround this somehow.
The problem here is, I have no clue if there's anything in the DLL
which would be indicative of the original image base address after
rebasing. Unless, maybe, some of the dwarf2 info itself can be
used to reconstruct the originl address?
Thanks,
Corinna
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-13 19:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 5:36 [Bug win32/18027] New: " corinna at vinschen dot de
2015-02-26 9:39 ` [Bug win32/18027] " asmwarrior at gmail dot com
2023-02-11 17:48 ` tromey at sourceware dot org
2023-02-12 12:20 ` ssbssa at sourceware dot org
2023-02-13 10:31 ` corinna at vinschen dot de
2023-02-13 10:36 ` corinna at vinschen dot de
2023-02-13 14:01 ` simark at simark dot ca
2023-02-13 16:17 ` corinna at vinschen dot de
2023-02-13 17:13 ` simark at simark dot ca
2023-02-13 17:24 ` ssbssa at sourceware dot org
2023-02-13 19:23 ` tromey at sourceware dot org
2023-02-13 19:46 ` ssbssa at sourceware dot org
2023-02-13 19:48 ` corinna at vinschen dot de [this message]
2023-02-13 22:08 ` tromey at sourceware dot org
2023-02-15 10:22 ` corinna at vinschen dot de
2023-02-17 2:15 ` tromey at sourceware dot org
2023-02-28 14:43 ` tromey at sourceware dot org
2023-02-28 15:20 ` corinna at vinschen dot de
2023-02-28 15:22 ` corinna at vinschen dot de
2023-03-24 17:31 ` tromey at sourceware dot org
2023-03-24 19:00 ` corinna at vinschen dot de
2023-03-27 9:19 ` nickc at redhat dot com
2023-03-28 8:58 ` corinna at vinschen dot de
2023-03-28 14:01 ` nickc at redhat dot com
2023-03-28 18:10 ` corinna at vinschen dot de
2023-03-29 12:46 ` tromey at sourceware dot org
2023-03-30 9:23 ` corinna at vinschen dot de
2023-03-30 9:24 ` corinna at vinschen dot de
2023-04-21 16:38 ` tromey at sourceware dot org
2023-04-21 16:54 ` tromey at sourceware dot org
2023-04-21 17:11 ` tromey at sourceware dot org
2023-04-21 19:48 ` corinna at vinschen dot de
2023-04-24 15:54 ` tromey at sourceware dot org
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=bug-18027-4717-n0s6mmI4Gy@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).