From: Jon Turney <jon.turney@dronecode.org.uk>
To: gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Fix a crash with a malformed PE header
Date: Fri, 03 Jan 2020 13:11:00 -0000 [thread overview]
Message-ID: <39b8efed-e23e-db20-4b28-332ceda2d8df@dronecode.org.uk> (raw)
In-Reply-To: <835zhuj71c.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On 02/01/2020 13:56, Eli Zaretskii wrote:
>> From: Jon Turney <jon.turney@dronecode.org.uk>
>> Cc: Jon Turney <jon.turney@dronecode.org.uk>
>> Date: Thu, 2 Jan 2020 12:54:05 +0000
>>
>> --- a/gdb/coff-pe-read.c
>> +++ b/gdb/coff-pe-read.c
>> @@ -441,6 +441,12 @@ read_pe_exported_syms (minimal_symbol_reader &reader,
>> }
>> }
>>
>> + if (expptr == 0)
>> + {
>> + /* no section contains export table rva */
>> + return;
>> + }
>> +
>
> Thanks. Would it make sense to produce some diagnostic output here,
> when an appropriate debug-FOO option is set?
Yes, I suppose that's better than just a comment.
How about the attached?
[-- Attachment #2: 0001-Fix-a-crash-with-a-malformed-PE-header.patch --]
[-- Type: text/plain, Size: 1331 bytes --]
From b78ee5736d93d7fa3476a69cc11229c047f477ec Mon Sep 17 00:00:00 2001
From: Jon Turney <jon.turney@dronecode.org.uk>
Date: Thu, 2 Jan 2020 00:25:56 +0000
Subject: [PATCH] Fix a crash with a malformed PE header
Don't try to read the PE export table when no section contains the RVA
for it.
(I have a PE executable [1] packed with UPX, where the export table data
directory entry contains a RVA which doesn't correspond to any section.
Mistakenly trying to debug this with gdb makes it crash.)
[1] https://cygwin.com/setup/setup-2.898.x86_64.exe
2020-01-02 Jon Turney <jon.turney@dronecode.org.uk>
* coff-pe-read.c (read_pe_exported_syms): Don't try to read the
export table if no section contains it's RVA.
---
gdb/ChangeLog | 5 +++++
gdb/coff-pe-read.c | 9 +++++++++
2 files changed, 14 insertions(+)
diff --git a/gdb/coff-pe-read.c b/gdb/coff-pe-read.c
index b05357bb8b..926db57e58 100644
--- a/gdb/coff-pe-read.c
+++ b/gdb/coff-pe-read.c
@@ -441,6 +441,15 @@ read_pe_exported_syms (minimal_symbol_reader &reader,
}
}
+ if (expptr == 0)
+ {
+ if (debug_coff_pe_read)
+ fprintf_unfiltered (gdb_stdlog, _("No section contains export RVA for "
+ "dll \"%s\"\n"),
+ dll_name);
+ return;
+ }
+
export_rva = export_opthdrrva;
export_size = export_opthdrsize;
--
2.21.0
next prev parent reply other threads:[~2020-01-03 13:11 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 [this message]
2020-01-03 13:20 ` Eli Zaretskii
2020-01-03 16:53 ` Tom Tromey
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=39b8efed-e23e-db20-4b28-332ceda2d8df@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=eliz@gnu.org \
--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