[PATCH] coff: Ignore corrupt relocation table

Alan Modra amodra@gmail.com
Sun Sep 21 22:14:29 GMT 2025


On Sun, Sep 21, 2025 at 07:52:01PM +0200, Jan Beulich wrote:
> On 21.09.2025 13:45, H.J. Lu wrote:
> > On Sun, Sep 21, 2025 at 6:12 PM Alan Modra <amodra@gmail.com> wrote:
> >> On Sun, Sep 21, 2025 at 03:47:11PM +0800, H.J. Lu wrote:
> >>> Any comments or objections?
> >>
> >> All three of your patches for these fuzzed object file linker bugs
> >> reduce the capability of the binutils to display corrupted object
> > 
> > Such information displayed by binutils is unreliable and corrupted
> > objects may lead to corrupted executable.   I think benefits of
> > such corrupted information are very limited if any.
> 
> I agree with Alan. Corruption or anomalies may be diagnosed (by
> warnings, in particular when linking), but we still should aim at
> displaying to users whatever we can sensibly display.

Yes, it would be quite OK to refuse to link objects that are
corrupted, but we shouldn't refuse to objdump them.

-- 
Alan Modra


More information about the Binutils mailing list