public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ricky at rzhou dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/25874] Printing variables after noreturn functions uses the wrong DWARF info
Date: Sat, 25 Apr 2020 09:42:40 +0000 [thread overview]
Message-ID: <bug-25874-4717-Xm41NQAYzV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25874-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25874
Ricky Zhou <ricky at rzhou dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Ricky Zhou <ricky at rzhou dot org> ---
Upon further reading, this looks like a duplicate of bug 25143 (see also the
corresponding Clang bug, https://bugs.llvm.org/show_bug.cgi?id=39752).
Looking at some of the discussion linked from the LLVM bug
(http://lists.dwarfstd.org/pipermail/dwarf-discuss-dwarfstd.org/2018-December/004500.html)
it looks like the correctness of fudging PC values is much more controversial
than I could have imagined!
I now see that doing so does resolve the ambiguity between "right after the
last instruction of a function" and "first instruction of the next function".
*** This bug has been marked as a duplicate of bug 25143 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-04-25 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 9:11 [Bug symtab/25874] New: Printing variables after noreturn functions use " ricky at rzhou dot org
2020-04-25 9:12 ` [Bug symtab/25874] Printing variables after noreturn functions uses " ricky at rzhou dot org
2020-04-25 9:14 ` ricky at rzhou dot org
2020-04-25 9:42 ` ricky at rzhou dot org [this message]
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-25874-4717-Xm41NQAYzV@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).