https://sourceware.org/bugzilla/show_bug.cgi?id=34865

            Bug ID: 34865
           Summary: GNU ld contradicts unsupported-symbol diagnostics with
                    error adding symbols: no error
           Product: binutils
           Version: 2.47
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: basavesh.shivakumar at wsu dot edu
  Target Milestone: ---

Created attachment 17184
  --> https://sourceware.org/bugzilla/attachment.cgi?id=17184&action=edit
repro

I'm reporting this bug on behalf of my team: Ananta Srikar Puranam, Emily West,
Dr. Swarn Priya, Dr. Peng Gao and Dr. Basavesh Ammanaghatta Shivakumar.

Summary
=======

GNU ld 2.47 and current head correctly reject reserved symbol binding 5 and
undefined symbol type 7, but in both cases append the contradictory diagnostic
"error adding symbols: no error"; a shared one-byte st_info control links
silently.

Reproduction
============

1. Download and extract
`bfd-unsupported-symbol-no-error-diagnostic-reproducer.tar.gz`.
2. Run the following command with an ld.bfd or all-target `ld-new` binary that
   supports the emulation used by the reproducer:

       LD_BFD=/path/to/ld-new sh repro.sh

The archive contains the fixed input files, independent controls, helper
scripts needed by `repro.sh`, and their checksums. The script uses a temporary
directory and does not modify the source tree.

Observed result
===============

GNU ld 2.47 and current head correctly reject reserved symbol binding 5 and
undefined symbol type 7, but in both cases append the contradictory diagnostic
"error adding symbols: no error"; a shared one-byte st_info control links
silently.

Expected result
===============

GNU ld should either produce the correct output or reject the input with a
normal diagnostic. It should not crash, hang, execute undefined behavior, read
outside an input-derived allocation, or produce the described malformed
output.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to