public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/104463] Split debug info not loaded from .debug/ if .gnu_debuglink points to binary itself
Date: Fri, 25 Feb 2022 12:39:01 +0000 [thread overview]
Message-ID: <bug-104463-4-H0Tj7DgYdk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104463-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104463
Mark Wielaard <mark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2022-02-25
--- Comment #1 from Mark Wielaard <mark at gcc dot gnu.org> ---
Note. The term "split dwarf" is often associated with the -gsplit-dwarf option,
which uses .dwo sections (and files) to split DWARF debuginfo. This bug isn't
about that.
I can replicate the issue, but haven't fully traced why it happens.
It seems libbacktrace gets confused about where /proc/self/exe points to and
tries to open /proc/self/bug, /proc/self/.debug/bug and
/usr/lib/debug//proc/self/bug
prev parent reply other threads:[~2022-02-25 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 12:34 [Bug libbacktrace/104463] New: " matti.niemenmaa+gccbugs at iki dot fi
2022-02-25 12:39 ` mark at gcc dot gnu.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-104463-4-H0Tj7DgYdk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).