From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: Benjamin Gilbert <bgilbert@backtick.net>, gdb@sourceware.org
Subject: Re: Trying to get GDB to find PE symbol file via build-id
Date: Mon, 16 Mar 2015 15:41:00 -0000 [thread overview]
Message-ID: <5506F9B1.9050008@dronecode.org.uk> (raw)
In-Reply-To: <54FDCDF0.6080602@dronecode.org.uk>
On 09/03/2015 16:44, Jon TURNEY wrote:
> On 08/03/2015 22:52, Benjamin Gilbert wrote:
>> I'm trying to build a Win32 DLL with separate debug symbols, but I can't
>> seem to get GDB to automatically load a symbol file using the PE build-id
>> support added in ld 2.25. I'm running on Fedora 21 x86_64, with a gdb
>> built from binutils-gdb HEAD (3e95021) and configured with
>> "--target=i686-w64-mingw32".
>
> Sorry, this was not something that I needed, so I never got around to
> looking at what was needed to hook this up in gdb.
>
> At the moment, fetching the build-id for gdb is only implemented for ELF
> files (See gdb/build-ic.c:build_id_bfd_get())
>
> It should be pretty straightforward to extend that to handle PE files as
> well, and add an interface to get the PE build-id out of BFD...
Well, slightly less straightforward than I thought it would be, but I
wrote a patch to do that...
[1] https://sourceware.org/ml/gdb-patches/2015-03/msg00458.html
next prev parent reply other threads:[~2015-03-16 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFKqAcT3qbRGNrczTyPpVW7vrm2GhVUbWVuhupn1YYwEQCOomA@mail.gmail.com>
2015-03-09 16:44 ` Jon TURNEY
2015-03-16 15:41 ` Jon TURNEY [this message]
2015-03-19 5:05 ` Benjamin Gilbert
2015-03-19 6:31 ` asmwarrior
2015-03-19 6:53 ` asmwarrior
2015-03-19 12:23 ` Jon TURNEY
2015-03-08 22:57 Benjamin Gilbert
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=5506F9B1.9050008@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=bgilbert@backtick.net \
--cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).