From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Find debug symbols file by buildid for PE file format also
Date: Wed, 22 Apr 2015 13:41:00 -0000 [thread overview]
Message-ID: <5537A51A.6040307@dronecode.org.uk> (raw)
In-Reply-To: <55251C45.4070006@dronecode.org.uk>
On 08/04/2015 13:17, Jon TURNEY wrote:
> On 17/03/2015 12:56, Jon TURNEY wrote:
>> On 16/03/2015 16:30, Eli Zaretskii wrote:
>> [...]
>>>>
>>>> gdb/doc/ChangeLog:
>>>>
>>>> 2015-03-14 Jon TURNEY <jon.turney@dronecode.org.uk>
>>>>
>>>> * gdb.texinfo (Separate Debug Files): Document that COFF is also
>>>> supported.
>>>
>>> The gdb.texinfo part is OK, except that AFAIK PE is not the same as
>>> COFF, so I suggest to amend the ChangeLog entry above.
>>
>> Yes, this should say PE in the ChangeLog (and subject).
>
> Updated patch attached.
Ping?
next prev parent reply other threads:[~2015-04-22 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:37 [PATCH] Find debug symbols file by buildid for coff " Jon TURNEY
2015-03-16 16:30 ` Eli Zaretskii
2015-03-17 12:56 ` Jon TURNEY
2015-04-08 12:17 ` [PATCH] Find debug symbols file by buildid for PE " Jon TURNEY
2015-04-08 12:39 ` Eli Zaretskii
2015-04-22 13:41 ` Jon TURNEY [this message]
2015-06-02 13:33 ` Jon TURNEY
2015-06-09 19:36 ` Joel Brobecker
2015-06-10 14:26 ` [PATCH] Allow gdb to find debug symbols file by build-id " Jon Turney
2015-06-12 15:45 ` Nicholas Clifton
2015-06-15 16:34 ` Mike Frysinger
2015-06-15 18:13 ` Andreas Schwab
2015-06-15 18:25 ` Jon TURNEY
2015-06-16 11:35 ` Nicholas Clifton
2015-06-17 16:09 ` Yao Qi
2015-06-18 11:05 ` Jon TURNEY
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=5537A51A.6040307@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=gdb-patches@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).