From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 39CCD384640E; Wed, 24 Apr 2024 23:36:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 39CCD384640E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1714001801; bh=MBgq9p7BWS1uUy9ILbibQMfRpJc9pwOVrwvi8tYs1Hc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qG6lC1kmuLLkn137h/UEaI/HGmn6oYmiQkGIrza+R2NABBKjE2gKqWijqRyjxBf6n Nd1FqGSnJPa73lyAsKBGGKHaQFqiKRdHOpj1tamMbpTq9NSt8pplaLjHM0DSogG6kj Hhh9vlywQi3s3PSC1z8/FokxBir07hbJBD0j3IZs= From: "dominik.b.czarnota+bugzilla at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 13.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominik.b.czarnota+bugzilla at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31669 --- Comment #5 from Disconnect3d --- (In reply to Andreas Schwab from comment #4) > Since __dso_handle does not have a size and no other hint is available, g= db > 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 ar= ound 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=