|
From: | jon.turney at dronecode dot org.uk |
Subject: | [Bug binutils/20193] New: Invalid executable after adding debuglink to an executable produced after merging PE resource sections |
Date: | Thu, 02 Jun 2016 16:52:39 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=20193 Bug ID: 20193 Summary: Invalid executable after adding debuglink to an executable produced after merging PE resource sections Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: jon.turney at dronecode dot org.uk Target Milestone: --- Created attachment 9304 --> https://sourceware.org/bugzilla/attachment.cgi?id=9304&action=edit Test case It looks like merging of resource sections which are non-trivial occasionally produces executables which are invalid after further manipulation, e.g. after stripping and adding a debuglink section Attached testcase demonstrates this, on x86_64. 1.exe and 2.exe are valid, but Windows refuses to run 3.exe as an invalid executable. -- You are receiving this mail because: You are on the CC list for the bug.
[Prev in Thread] | Current Thread | [Next in Thread] |