From: "godlygeek at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/29430] `dwarf_getscopes` fails after a8493c1
Date: Fri, 29 Jul 2022 18:53:13 +0000 [thread overview]
Message-ID: <bug-29430-10460-2ew6XMlhuh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29430-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29430
Matt Wozniski <godlygeek at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |NOTABUG
--- Comment #1 from Matt Wozniski <godlygeek at gmail dot com> ---
Well - nevermind. Our problem turned out not to be an issue with
`dwarf_getscopes` at all, but a bug in our unwinder that only occurred when
`dwarf_getscopes` finds 0 scopes. Our buggy code was working with elfutils
0.179 because `dwarf_getscopes` would erroneously return extra scopes due to
DIE trees being visited multiple times, and we'd ignore those scopes because
`dwarf_tag(scope) != DW_TAG_inlined_subroutine`, but our bug that triggers only
when 0 scopes are found wouldn't occur.
After `dwarf_getscopes` was fixed, it began returning 0 when it previously
hadn't, and our code failed to properly handle that case in a way that had
never been noticed.
Sorry for the false alarm!
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-07-29 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 22:02 [Bug libdw/29430] New: " godlygeek at gmail dot com
2022-07-29 18:53 ` godlygeek at gmail dot com [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-29430-10460-2ew6XMlhuh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).