From: Tom Tromey <tom@tromey.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Fix a crash with a malformed PE header
Date: Fri, 03 Jan 2020 16:53:00 -0000 [thread overview]
Message-ID: <87png0traf.fsf@tromey.com> (raw)
In-Reply-To: <39b8efed-e23e-db20-4b28-332ceda2d8df@dronecode.org.uk> (Jon Turney's message of "Fri, 3 Jan 2020 13:11:24 +0000")
>>>>> "Jon" == Jon Turney <jon.turney@dronecode.org.uk> writes:
Jon> 2020-01-02 Jon Turney <jon.turney@dronecode.org.uk>
Jon> * coff-pe-read.c (read_pe_exported_syms): Don't try to read the
Jon> export table if no section contains it's RVA.
Thanks. This is ok.
Tom
prev parent reply other threads:[~2020-01-03 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 12:54 Jon Turney
2020-01-02 13:56 ` Eli Zaretskii
2020-01-03 13:11 ` Jon Turney
2020-01-03 13:20 ` Eli Zaretskii
2020-01-03 16:53 ` Tom Tromey [this message]
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=87png0traf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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