From: Norbert Lange <nolange79@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
gdb@sourceware.org, Gary Benson <gbenson@redhat.com>
Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally?
Date: Mon, 6 Apr 2020 13:31:43 +0200 [thread overview]
Message-ID: <CADYdroPyrFuxmOW5idVmfY9N0Yrpma0CNORZiEkzuX+EmV8e6A@mail.gmail.com> (raw)
In-Reply-To: <20200330091934.GA1078028@host1.jankratochvil.net>
Am Mo., 30. März 2020 um 11:19 Uhr schrieb Jan Kratochvil
<jan.kratochvil@redhat.com>:
>
> On Mon, 30 Mar 2020 11:04:30 +0200, Norbert Lange wrote:
> > I would want to use 'set sysroot /path/to/staging/dir', but the downside is that
> > mismatches will not be detected and can badly mess up debugging.
>
> You should have setup symlinks in /usr/lib/debug/.build-id/
> (or where you 'set debug-file-directory') for all build-ids you ever build.
> That works for core-files.
Thats the plan.
I verified that the coredump contains all Build-Ids with
eu-unstrip -n --core /tmp/core
But Id have to first locate the binary manually, then starting
gdb PATH_TO_BINARY PATH_TO_CORE
Whats worse is, that gdb seems to lookup for the library first (filepath),
if it exists it will use the Build-Id from this potentially unrelated
version (and use the wrong debug info if one exists),
if it does not exist, then it wont even try searching in the
debug-library (neither via name or build-id).
In other words, its completely broken unless the system you debug is
the very same (and in the same state) as the executable did run on.
If I'd want to debug a coredump now, I would have to inspect the
buildids, copy the debug-infos under the name they where used on the
target in a own sysroot.
(Almost the same as for remote debug now).
I tried both with sysroot unset (default) and set to a directory with
partially missing/outdated versions.
> > GDB 9.0 certainly does not use *Build-Ids from the 'remote'*,
>
> According to a test I have made now I agree. Maybe Gary Benson will suggest
> more.
Norbert
next prev parent reply other threads:[~2020-04-06 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 14:20 Norbert Lange
2020-03-28 0:40 ` Frank Ch. Eigler
2020-03-30 8:35 ` Norbert Lange
2020-03-30 8:45 ` Jan Kratochvil
2020-03-30 9:04 ` Norbert Lange
2020-03-30 9:19 ` Jan Kratochvil
2020-03-30 18:43 ` Gary Benson
2020-04-06 11:31 ` Norbert Lange [this message]
2020-04-06 11:49 ` Jan Kratochvil
2020-04-06 12:08 ` Norbert Lange
2020-04-06 12:16 ` Jan Kratochvil
2020-04-06 12:53 ` Norbert Lange
2020-04-06 14:41 ` Norbert Lange
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=CADYdroPyrFuxmOW5idVmfY9N0Yrpma0CNORZiEkzuX+EmV8e6A@mail.gmail.com \
--to=nolange79@gmail.com \
--cc=fche@redhat.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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).