From: asmwarrior <asmwarrior@gmail.com>
To: Benjamin Gilbert <bgilbert@backtick.net>,
Jon TURNEY <jon.turney@dronecode.org.uk>
Cc: gdb@sourceware.org
Subject: Re: Trying to get GDB to find PE symbol file via build-id
Date: Thu, 19 Mar 2015 06:31:00 -0000 [thread overview]
Message-ID: <550A6ED0.2030000@gmail.com> (raw)
In-Reply-To: <CAFKqAcR0xxj6Rj_tOU7bDuLQcZTCboQ+Ohv6WyERs7MYwkUfPA@mail.gmail.com>
On 2015-3-19 13:05, Benjamin Gilbert wrote:
> On Mon, Mar 16, 2015 at 11:41 AM, Jon TURNEY
> <jon.turney@dronecode.org.uk> wrote:
>> On 09/03/2015 16:44, Jon TURNEY wrote:
>>> 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
>
> Your patch works for me.
>
Do you know there are any native compiler suite under Windows which support "build-id" option?
I just tried recent native MinGW and MinGW-W64 compiler suite, the ld.exe in those suites doesn't supoort this option.
Yuanhui Zhang
next prev parent reply other threads:[~2015-03-19 6:31 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
2015-03-19 5:05 ` Benjamin Gilbert
2015-03-19 6:31 ` asmwarrior [this message]
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=550A6ED0.2030000@gmail.com \
--to=asmwarrior@gmail.com \
--cc=bgilbert@backtick.net \
--cc=gdb@sourceware.org \
--cc=jon.turney@dronecode.org.uk \
/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).