public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29159] New: gdb crashes when libstdc++ debuginfo is present but .dwz is missing
Date: Fri, 20 May 2022 00:38:12 +0000 [thread overview]
Message-ID: <bug-29159-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29159
Bug ID: 29159
Summary: gdb crashes when libstdc++ debuginfo is present but
.dwz is missing
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: amerey at redhat dot com
Target Milestone: ---
gdb crashes when libstdc++ debuginfo is present but the libstdc++ .dwz file is
missing.
This condition can be triggered by installing the libstdc++ debuginfo package
and manually moving the .dwz file so gdb can't find it. Alternatively, allow
debuginfod to download the libstdc++ debuginfo but cancel the .dwz file
download (press ctrl-c during the download).
Steps to Reproduce:
$ gdb -ex 'run' gdb
[...]
Downloading separate debug info for /lib64/libstdc++.so.6...
Downloading separate debug info for
/home/amerey/.cache/debuginfod_client/36f7946c2608f3e08b11ec0af0b63055a39c89f3/debuginfo...
Cancelling download of separate debug info for
/home/amerey/.cache/debuginfod_client/36f7946c2608f3e08b11ec0af0b63055a39c89f3/debuginfo...
[...]
Starting program: /usr/bin/gdb
Error while reading shared library symbols for /lib64/libstdc++.so.6:
could not find '.gnu_debugaltlink' file for
/home/amerey/.cache/debuginfod_client/36f7946c2608f3e08b11ec0af0b63055a39c89f3/debuginfo
[...]
double free or corruption (!prev)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-05-20 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 0:38 amerey at redhat dot com [this message]
2024-04-06 15:37 ` [Bug gdb/29159] " tromey at sourceware 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-29159-4717@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).