public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "k4lizen at proton dot me" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31669] wrong "info symbol" output, symbol shadowing, __dso_handle
Date: Thu, 25 Apr 2024 16:54:59 +0000	[thread overview]
Message-ID: <bug-31669-4717-SHmQFZ3T6T@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 #6 from k4lizen <k4lizen at proton dot me> ---
> 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.

It would probably make sense to say in the output of `info symbol` that gdb is
guessing it because there is no symbol size information (how commonly is this
the case?).

It would allow both users to not be confused, and pwndbg could check if the
output of the command contains the message and proceed accordingly.

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

  parent reply	other threads:[~2024-04-25 16:55 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
2024-04-25 16:54 ` k4lizen at proton dot me [this message]
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-SHmQFZ3T6T@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).