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

            Bug ID: 33474
           Summary: [BUG] A SEGV in init_reloc_cookie at elflink.c:13877
           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 16372
  --> https://sourceware.org/bugzilla/attachment.cgi?id=16372&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

==149207==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000348 (pc
0x00000077fcdf bp 0x7ffc7bc63790 sp 0x7ffc7bc63570 T0)
==149207==The signal is caused by a READ memory access.
==149207==Hint: address points to the zero page.
    #0 0x77fcdf in init_reloc_cookie
/benchmark/bin/binutils-2.45/bfd/elflink.c:13877:12
    #1 0x77c9de in init_reloc_cookie_for_section
/benchmark/bin/binutils-2.45/bfd/elflink.c:13960:8
    #2 0x780bc7 in bfd_elf_gc_sections
/benchmark/bin/binutils-2.45/bfd/elflink.c:14681:21
    #3 0x5131a8 in lang_gc_sections
/benchmark/bin/binutils-2.45/ld/ldlang.c:7892:5
    #4 0x50c94d in lang_process /benchmark/bin/binutils-2.45/ld/ldlang.c:8542:3
    #5 0x53ca89 in main /benchmark/bin/binutils-2.45/ld/./ldmain.c:882:3
    #6 0x7f9fbd904082 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x24082)
    #7 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/elflink.c:13877:12 in init_reloc_cookie
==149207==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