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

            Bug ID: 33466
           Summary: [BUG] A SEGV in _bfd_elf_write_section_eh_frame at
                    elf-eh-frame.c:2166
           Product: binutils
           Version: 2.45
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: yfzhang23 at stu dot pku.edu.cn
  Target Milestone: ---

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

## Description

- Version: Binutils 2.45 with patches in bug 33451, bug 33455, and bug 33457.
- Environment: Ubuntu 20.04.6 LTS, Clang 12.0.0

## Steps to reproduce

export CC="clang"
export CFLAGS="-g -fsanitize=address"
./configure
make -j
./ld/ld-new --gc-sections --no-print-gc-sections -w $POC

## Sanitizer output

==146908==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000030 (pc
0x0000007c1192 bp 0x7ffc802a2f70 sp 0x7ffc802a2300 T0)
==146908==The signal is caused by a READ memory access.
==146908==Hint: address points to the zero page.
    #0 0x7c1192 in _bfd_elf_write_section_eh_frame
/benchmark/bin/binutils-2.45/bfd/elf-eh-frame.c:2166:10
    #1 0x76c55f in elf_link_input_bfd
/benchmark/bin/binutils-2.45/bfd/elflink.c:12220:12
    #2 0x75b539 in bfd_elf_final_link
/benchmark/bin/binutils-2.45/bfd/elflink.c:13185:11
    #3 0x545133 in ldwrite /benchmark/bin/binutils-2.45/ld/ldwrite.c:548:8
    #4 0x53cc51 in main /benchmark/bin/binutils-2.45/ld/./ldmain.c:912:3
    #5 0x7fcacdbab082 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x24082)
    #6 0x41d6ad in _start (/benchmark/bin/binutils-2.45/ld/ld-new+0x41d6ad)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV
/benchmark/bin/binutils-2.45/bfd/elf-eh-frame.c:2166:10 in
_bfd_elf_write_section_eh_frame
==146908==ABORTING

## Credit

Reported by Yifan Zhang, [PLL](https://pl.cs.pku.edu.cn/en/)

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

Reply via email to