bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/21348] New: odr-violation in libiberty/safe-ctype.c


From: ago at gentoo dot org
Subject: [Bug ld/21348] New: odr-violation in libiberty/safe-ctype.c
Date: Sun, 02 Apr 2017 08:27:12 +0000

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

            Bug ID: 21348
           Summary: odr-violation in libiberty/safe-ctype.c
           Product: binutils
           Version: 2.29 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: ago at gentoo dot org
  Target Milestone: ---

During the compilation of libpng, while the configure script made some test I
hit a build failure:

configure:3313: x86_64-pc-linux-gnu-gcc -O2 -mtune=generic -march=x86-64
-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu -Wl,-z,lazy conftest.c  >&5
=================================================================
==32651==ERROR: AddressSanitizer: odr-violation (0x0000009ae8e0):
  [1] size=512 '_sch_istable'
/tmp/portage/sys-devel/binutils-9999/work/binutils/libiberty/safe-ctype.c:158:22
  [2] size=512 '_sch_istable'
/tmp/portage/sys-devel/binutils-9999/work/binutils/libiberty/safe-ctype.c:158:22
These globals were registered at these points:
  [1]:
    #0 0x4321c0  (/usr/x86_64-pc-linux-gnu/binutils-bin/git/as+0x4321c0)
    #1 0x7f6648d226f8 
(/usr/lib64/binutils/x86_64-pc-linux-gnu/git/libopcodes-2.28.51.20170401.so+0x1136f8)

  [2]:
    #0 0x4321c0  (/usr/x86_64-pc-linux-gnu/binutils-bin/git/as+0x4321c0)
    #1 0x7f6648671808 
(/usr/lib64/binutils/x86_64-pc-linux-gnu/git/libbfd-2.28.51.20170401.so+0x104b808)

==32651==HINT: if you don't care about these errors you may set
ASAN_OPTIONS=detect_odr_violation=0
SUMMARY: AddressSanitizer: odr-violation: global '_sch_istable' at
/tmp/portage/sys-devel/binutils-9999/work/binutils/libiberty/safe-ctype.c:158:22

-- 
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]