[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/26432] New: ASAN error: in bfd_getb32 /home/mliska/Program

From: mliska at suse dot cz
Subject: [Bug binutils/26432] New: ASAN error: in bfd_getb32 /home/mliska/Programming/binutils/bfd/libbfd.c:631
Date: Thu, 20 Aug 2020 12:15:14 +0000


            Bug ID: 26432
           Summary: ASAN error: in bfd_getb32
           Product: binutils
           Version: 2.34
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: mliska at suse dot cz
  Target Milestone: ---

The following fails when I build binutils with:
configure --build=x86_64-linux --disable-nls --disable-gdb --disable-gdbserver
--disable-sim --disable-readline --disable-libdecnumber --enable-obsolete
--target=armeb-linuxeabi CFLAGS="-g -O2 -fsanitize=address,undefined
-Wno-error" CXXLAGS="-g -O2 -fsanitize=address,undefined -Wno-error"
Target: armeb-linuxeabi
FAIL: callweak
Executing on host: sh -c {/dev/shm/tbh4lqi8/ld/ld-new   -o
tmpdir/reloc-boundaries -z norelro
-L/home/mliska/Programming/binutils/ld/testsuite/ld-arm -defsym x=0 -defsym y=0
-defsym _start=0 tmpdir/reloc-boundaries.o  2>&1}  /dev/null ld.tmp (timeout =
==57326==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x6020000029d6 at pc 0x00000051b416 bp 0x7fffffffae10 sp 0x7fffffffae08
    #0 0x51b415 in bfd_getb32
    #1 0x5d5343 in elf32_arm_final_link_relocate
    #2 0x5ff0ae in elf32_arm_relocate_section
    #3 0x760aaa in elf_link_input_bfd
    #4 0x76f04c in bfd_elf_final_link
    #5 0x5c0cad in elf32_arm_final_link
    #6 0x49cd19 in ldwrite /home/mliska/Programming/binutils/ld/ldwrite.c:545
    #7 0x415649 in main /home/mliska/Programming/binutils/ld/ldmain.c:510
    #8 0x7ffff6adacc9 in __libc_start_main (/lib64/libc.so.6+0x26cc9)
    #9 0x417b29 in _start (/dev/shm/tbh4lqi8/ld/ld-new+0x417b29)

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]