From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
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:31:00 -0000 [thread overview]
Message-ID: <20111014172907.GB4939@host1.jankratochvil.net> (raw)
In-Reply-To: <201110141307.54843.vapier@gentoo.org>
On Fri, 14 Oct 2011 19:07:53 +0200, Mike Frysinger wrote:
> that's why it was a hack. i think it reasonable that if there is no debug
> info to first look for the file name itself, and then look for the file name with
> a .debug suffix.
The debug files without any suffix are IMO problematic, there was already at
least a second patch to deal with it and it has performance issues:
[patch] Verify byte-by-byte if both files are the same on "remote:" [Re: [rfc] False separate debuginfo warning with "remote:" access]
http://sourceware.org/ml/gdb-patches/2011-10/msg00254.html
build-id should be the first one tried, it is already tried if .debug_link
exists so why to break it for the non-.debug_link case. If build-id does not
exist I do not mind much how many ineffective fallbacks in which order get
implemented.
Regards,
Jan
next prev parent reply other threads:[~2011-10-14 17:29 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:37 ` Mike Frysinger
2011-10-14 15:27 ` 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
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 [this message]
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=20111014172907.GB4939@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=aristovski@qnx.com \
--cc=gdb@sources.redhat.com \
--cc=vapier@gentoo.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