public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dominik.b.czarnota+bugzilla at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31669] wrong "info symbol" output, symbol shadowing, __dso_handle
Date: Wed, 24 Apr 2024 22:09:04 +0000 [thread overview]
Message-ID: <bug-31669-4717-M6h6TI3fEF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31669-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31669
--- Comment #3 from Disconnect3d <dominik.b.czarnota+bugzilla at gmail dot com> ---
Also:
```
pwndbg> info symbol 0x402008+2748
__dso_handle + 2748 in section .rodata
pwndbg> info symbol 0x402008+2749
No symbol matches 0x402008+2749.
pwndbg> info symbol 0x402008+2750
No symbol matches 0x402008+2750.
pwndbg> info symbol 0x402008+2751
No symbol matches 0x402008+2751.
pwndbg> info symbol 0x402008+2752
__GNU_EH_FRAME_HDR in section .eh_frame_hdr
```
It seems that GDB creates symbols for each address past a given symbol address
until 4 bytes before another symbol?
It would be nice to be able to:
1) disable this behavior
2) have a way to query for symbols around a given address, e.g. 0x402008+2751
should show us the symbols/addresses of `__dso_handle` and `__GNU_EH_FRAME_HDR`
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-24 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 12:31 [Bug gdb/31669] New: " k4lizen at proton dot me
2024-04-22 12:34 ` [Bug gdb/31669] " k4lizen at proton dot me
2024-04-24 22:02 ` dominik.b.czarnota+bugzilla at gmail dot com
2024-04-24 22:09 ` dominik.b.czarnota+bugzilla at gmail dot com [this message]
2024-04-24 22:27 ` schwab@linux-m68k.org
2024-04-24 23:36 ` dominik.b.czarnota+bugzilla at gmail dot com
2024-04-25 16:54 ` k4lizen at proton dot me
2024-04-26 14:39 ` sam at gentoo 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-31669-4717-M6h6TI3fEF@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).