From: Mike Frysinger <vapier@gentoo.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Aleksandar Ristovski <aristovski@qnx.com>, gdb@sources.redhat.com
Subject: Re: working with split debug files and sectionless ELFs
Date: Fri, 14 Oct 2011 17:08:00 -0000 [thread overview]
Message-ID: <201110141305.47508.vapier@gentoo.org> (raw)
In-Reply-To: <20111014162531.GA978@host1.jankratochvil.net>
[-- Attachment #1: Type: Text/Plain, Size: 889 bytes --]
On Friday 14 October 2011 12:25:31 Jan Kratochvil wrote:
> On Fri, 14 Oct 2011 17:49:24 +0200, Jan Kratochvil wrote:
> > Using the ".debug" extension is too slow as the file needs to be
> > checksummed first. One should use /usr/lib/debug/.build-id/ instead.
> > Still the argument applies even /usr/lib/debug/.build-id/ is skipped
> > without .debug_link. But for /usr/lib/debug/.build-id/ you do not need
> > to assume any ".debug" suffix.
>
> That's not true - one can check just the build-id note even if one finds it
> by the ".debug" suffix; just GDB currently does not do so. Although I do
> not think it is useful in any way - if build-id is already present it can
> be used for the filename as it prevents name clashes during multiple
> versions installed, moved files etc.
build-id is a section. my ELF has no sections. i'm back where i started :).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-14 17:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 17:36 Mike Frysinger
2011-10-14 14:23 ` Aleksandar Ristovski
2011-10-14 15:27 ` Mike Frysinger
2011-10-14 15:37 ` Mike Frysinger
2011-10-14 15:42 ` Aleksandar Ristovski
2011-10-14 16:00 ` Jan Kratochvil
2011-10-14 16:47 ` Jan Kratochvil
2011-10-14 17:08 ` Mike Frysinger [this message]
2011-10-14 17:29 ` Jan Kratochvil
2011-10-15 5:28 ` Mike Frysinger
2011-10-14 17:20 ` Mike Frysinger
2011-10-14 17:31 ` Jan Kratochvil
2011-10-14 17:34 ` Aleksandar Ristovski
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=201110141305.47508.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=aristovski@qnx.com \
--cc=gdb@sources.redhat.com \
--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).