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 23:36:41 +0000	[thread overview]
Message-ID: <bug-31669-4717-M1HpjUSe7f@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 #5 from Disconnect3d <dominik.b.czarnota+bugzilla at gmail dot com> ---
(In reply to Andreas Schwab from comment #4)
> Since __dso_handle does not have a size and no other hint is available, gdb
> can only assume that it extends until the next symbol.

How does this logic really works? Is this that some kind of map entry is
created for each memory address in such a case?

Is there any way to disable this behavior or tell GDB to assume a size for
unknown sizes to be sizeof(pointer) or something like this?

Eventually, I think we want to have Python API for the two use cases I noted
earlier, so that we can "get symbol for given address" and "find symbols around
addresses".

For now I guess we can workaround this issue in Pwndbg by ignoring returned
symbols with "+" but this may be buggy...

I bet that if there is a symbol with known size, it can also appear/resolve in
GDB with symbol+offset as it is done here, heh.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-24 23:36 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
2024-04-24 22:27 ` schwab@linux-m68k.org
2024-04-24 23:36 ` dominik.b.czarnota+bugzilla at gmail dot com [this message]
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-M1HpjUSe7f@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).