From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Cc: Mike Frysinger <vapier@gentoo.org>
Subject: Re: working with split debug files and sectionless ELFs
Date: Fri, 14 Oct 2011 15:42:00 -0000 [thread overview]
Message-ID: <4E985776.5080002@qnx.com> (raw)
In-Reply-To: <201110141127.18567.vapier@gentoo.org>
On 11-10-14 11:27 AM, Mike Frysinger wrote:
> On Friday 14 October 2011 10:23:04 Aleksandar Ristovski wrote:
>> On 11-10-12 01:35 PM, Mike Frysinger wrote:
>>> second, i wonder if we can't have this work more intelligently out of the
>>> box. is it unreasonable to have gdb automatically search /usr/lib/debug/
>>> for split debuf files if the .gnu_debuglink section does not exist ? or
>>> at least do it if the ELF has no sections at all ? it'd be nice if we
>>> could do `gdb prog` and gdb is smart enough to at least check
>>> /usr/lib/debug/usr/bin/prog.debug. -mike
>>
>> Can this be used for what you want:
>>
>> (gdb) help set debug-file-directory
>
> that is already set to "/usr/lib/debug/" by default. if you look at the logic
> that loads the split debug files, the issue is that it immediately returns if
> no debugging information is found in the ELF -- which there isn't if all the
> sections have been split out. so it doesn't get a chance to scan the debug
> file directory.
>
> check out symfile.c:find_separate_debug_file_by_debuglink(). i hacked it locally
> so that when get_debug_link_info() returns NULL, the code would fall back to
> searching for the basename(argv[0]) + ".debug" of the ELF in question. that
> seemed to do what i want: "just work".
> -mike
Ok, so the problem is that if debuglink is missing, gdb just gives up.
FWIW, what you are proposing makes sense to me. Maybe make it an
optional behaviour?
I'd suggest you open an enhancement request in bugzilla (if there is not
something along those lines there already) and propose the patch so the
maintainers have a say.
---
Aleksandar
next prev parent reply other threads:[~2011-10-14 15:39 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 [this message]
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
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=4E985776.5080002@qnx.com \
--to=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