public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Norbert Lange <nolange79@gmail.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	gdb@sourceware.org
Subject: Re: Automatically fetching Build ID from remote libraries and resole them locally?
Date: Mon, 30 Mar 2020 19:43:25 +0100	[thread overview]
Message-ID: <20200330184324.GA21199@blade.nx> (raw)
In-Reply-To: <20200330091934.GA1078028@host1.jankratochvil.net>

Jan Kratochvil wrote:
> 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.
> 
> > 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.

Sorry to disappoint, but I don't think I've ever done anything with
build-id.

Cheers,
Gary


  reply	other threads:[~2020-03-30 18:43 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 [this message]
2020-04-06 11:31           ` Norbert Lange
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=20200330184324.GA21199@blade.nx \
    --to=gbenson@redhat.com \
    --cc=fche@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=nolange79@gmail.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).