[Bug ld/22126] [2.29 Regression] ld --unresolved-symbols ignore-all doesn't create a reference to undefined symbols
https://sourceware.org/bugzilla/show_bug.cgi?id=22126 Alan Modra changed: What|Removed |Added Status|WAITING |RESOLVED CC||amodra at gmail dot com Resolution|--- |WONTFIX --- Comment #2 from Alan Modra --- I had to go back to 2.26 to find a ld.bfd that emitted "this_symbol_might_be_undefined" without passing --emit-relocs to ld. Contrary to the original claims, that seems true on all targets too, not just x86_64. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/21880] Memory leak in demangle
https://sourceware.org/bugzilla/show_bug.cgi?id=21880 Dongliang Mu changed: What|Removed |Added CC||mudongliangabcd at gmail dot com --- Comment #4 from Dongliang Mu --- Hello Google AutoFuzz Team: I tried to reproduce this bug in the docker, but when I compiled demangle_fuzzer.cc. It encounters one error: $ $CXX $CXXFLAGS $LDFLAGS -I../include ../libiberty/demangle_fuzzer.cc libiberty.a -lFuzzer -o demangle_fuzzer In file included from ../libiberty/demangle_fuzzer.cc:5: In file included from ../include/demangle.h:32: ../include/libiberty.h:112:14: error: 'basename' is missing exception specification 'throw()' extern char *basename (const char *) ATTRIBUTE_RETURNS_NONNULL ATTRIBUTE_NONNULL(1); ^ throw() /usr/include/string.h:601:26: note: previous declaration is here extern "C++" const char *basename (const char *__filename) ^ 1 error generated. How do I fix this problem and then trigger the bug? Note, in the confguration of binutils, "--host" option is essential. The new Dockerfile for my case is https://gist.github.com/mudongliang/3c14d1c4937a9aa6035957f34adfe68f -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/21880] Memory leak in demangle
https://sourceware.org/bugzilla/show_bug.cgi?id=21880 --- Comment #5 from Dongliang Mu --- (In reply to Dongliang Mu from comment #4) > Hello Google AutoFuzz Team: > > I tried to reproduce this bug in the docker, but when I compiled > demangle_fuzzer.cc. It encounters one error: > > $ $CXX $CXXFLAGS $LDFLAGS -I../include ../libiberty/demangle_fuzzer.cc > libiberty.a -lFuzzer -o demangle_fuzzer > In file included from ../libiberty/demangle_fuzzer.cc:5: > In file included from ../include/demangle.h:32: > ../include/libiberty.h:112:14: error: 'basename' is missing exception > specification 'throw()' > extern char *basename (const char *) ATTRIBUTE_RETURNS_NONNULL > ATTRIBUTE_NONNULL(1); > ^ > throw() > /usr/include/string.h:601:26: note: previous declaration is here > extern "C++" const char *basename (const char *__filename) > ^ > 1 error generated. > > > How do I fix this problem and then trigger the bug? > -DHAVE_DECL_BASENAME is missing. Sorry for the noise. > Note, in the confguration of binutils, "--host" option is essential. > > The new Dockerfile for my case is > https://gist.github.com/mudongliang/3c14d1c4937a9aa6035957f34adfe68f -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/22163] New: null pointer dereference in elf_x86_64_get_synthetic_symtab, elf64-x86-64.c:6945 in binutils 2.29.1
https://sourceware.org/bugzilla/show_bug.cgi?id=22163 Bug ID: 22163 Summary: null pointer dereference in elf_x86_64_get_synthetic_symtab, elf64-x86-64.c:6945 in binutils 2.29.1 Product: binutils Version: 2.29 Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: luanjunchao at 163 dot com Target Milestone: --- Created attachment 10435 --> https://sourceware.org/bugzilla/attachment.cgi?id=10435&action=edit crash of elf When I run objdump with a specific elf, it crashes. The command I run is objdump -S crash.pdf, and the result is as follows: ASAN:SIGSEGV = ==82641==ERROR: AddressSanitizer: SEGV on unknown address 0x0008 (pc 0x00510f8a bp 0x7ffebb774a00 sp 0x7ffebb774720 T0) #0 0x510f89 in elf_x86_64_get_synthetic_symtab /work/binutils-2.29.1-asan/binutils-2.29.1/bfd/elf64-x86-64.c:6945 #1 0x4140d2 in dump_bfd objdump.c:3525 #2 0x4144a5 in display_object_bfd objdump.c:3603 #3 0x4148a1 in display_any_bfd objdump.c:3692 #4 0x414916 in display_file objdump.c:3713 #5 0x415925 in main objdump.c:4015 #6 0x7ff3314b782f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f) #7 0x403128 in _start (/work/binutils-2.29.1-asan/binutils-2.29.1/binutils/objdump+0x403128) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /work/binutils-2.29.1-asan/binutils-2.29.1/bfd/elf64-x86-64.c:6945 elf_x86_64_get_synthetic_symtab ==82641==ABORTING The crash elf is attached. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
