Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Subject: Re: working with split debug files and sectionless ELFs
Date: Fri, 14 Oct 2011 14:23:00 -0000	[thread overview]
Message-ID: <j79gkk$65e$1@dough.gmane.org> (raw)
In-Reply-To: <201110121335.56792.vapier@gentoo.org>

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
Set the directories where separate debug symbols are searched for.
Separate debug symbols are first searched for in the same
directory as the binary, then in the `.debug' subdirectory,
and lastly at the path of the directory of the binary with
each global debug-file-directory component prepended.






  reply	other threads:[~2011-10-14 14:23 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 [this message]
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
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='j79gkk$65e$1@dough.gmane.org' \
    --to=aristovski@qnx.com \
    --cc=gdb@sources.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