public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27570] New: gdb: missing support for debuginfod in core_target::build_file_mappings
Date: Fri, 12 Mar 2021 16:34:37 +0000 [thread overview]
Message-ID: <bug-27570-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27570
Bug ID: 27570
Summary: gdb: missing support for debuginfod in
core_target::build_file_mappings
Product: gdb
Version: HEAD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
Target Milestone: ---
It seems that gdb can't utilize debuginfod protocol to get debuginfo of
binaries and shared libs:
$ export DEBUGINFOD_URLS="http://foo.bar:8002" && gdb -ex 'core
12sp3-sssd.core.715'
...
warning: Can't open file /usr/sbin/sssd during file-backed mapping note
processing
warning: Can't open file /var/lib/sss/mcpath/initgroups (deleted) during
file-backed mapping note processing
warning: Can't open file /lib64/libnss_sss.so.2 during file-backed mapping note
processing
warning: Can't open file /lib64/libnsl-2.22.so during file-backed mapping note
processing
warning: Can't open file /lib64/libnss_compat-2.22.so during file-backed
mapping note processing
warning: Can't open file /usr/lib64/libtdb.so.1.3.12 during file-backed mapping
note processing
...
warning: Can't open file /lib64/ld-2.22.so during file-backed mapping note
processing
[New LWP 715]
Missing separate debuginfo for the main executable file
Try: zypper install -C
"debuginfo(build-id)=41b05d41005e68f89b5422f1683b26c332f2d2e6"
Core was generated by `/usr/sbin/sssd'.
#0 0x00007f529a0b9350 in ?? ()
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-12 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 16:34 mliska at suse dot cz [this message]
2021-03-12 16:34 ` [Bug gdb/27570] " mliska at suse dot cz
2021-03-12 17:09 ` mliska at suse dot cz
2021-03-15 13:45 ` mliska at suse dot cz
2021-03-15 13:58 ` mliska at suse dot cz
2021-03-15 14:07 ` fche at redhat dot com
2021-04-01 6:45 ` vries at gcc dot gnu.org
2021-04-01 11:08 ` fche at redhat dot com
2021-04-24 18:32 ` mark at klomp dot org
2021-08-06 1:34 ` lennordocdoc0921 at gmail dot com
2022-03-21 18:19 ` cvs-commit at gcc dot gnu.org
2022-03-22 12:13 ` mliska at suse dot cz
2022-03-22 18:48 ` amerey at redhat dot com
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-27570-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).