https://sourceware.org/bugzilla/show_bug.cgi?id=23247
Bug ID: 23247
Summary: Segfault in 0.171 RC1 release candidate
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Created attachment 11047
--> https://sourceware.org/bugzilla/attachment.cgi?id=11047&action=edit
test-case
I've just built elftuils with GCC 8.1.0 and I see:
$ LD_LIBRARY_PATH=./libdw/ ./src/readelf -a -w ./backends/libebl_x86_64.so
[snip]
DWARF section [32] '.debug_loc' at offset 0x2fbd9:
CU [ 2d] base: +0x0000000000001e60 <x86_64_reloc_type_name>
Segmentation fault (core dumped)
Valgrind tells:
DWARF section [32] '.debug_loc' at offset 0x2fbd9:
CU [ 2d] base: +0x0000000000001e60 <x86_64_reloc_type_name>
==19867== Invalid read of size 8
==19867== at 0x41EC14: next_listptr_offset (readelf.c:4939)
==19867== by 0x41EC14: print_debug_loc_section (readelf.c:9247)
==19867== by 0x4122D8: print_debug (readelf.c:11075)
==19867== by 0x415610: process_elf_file (readelf.c:980)
==19867== by 0x41631C: process_dwflmod (readelf.c:744)
==19867== by 0x4E62020: dwfl_getmodules (dwfl_getmodules.c:86)
==19867== by 0x40883B: process_file (readelf.c:852)
==19867== by 0x4044C3: main (readelf.c:338)
==19867== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==19867==
==19867==
==19867== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==19867== Access not within mapped region at address 0x0
==19867== at 0x41EC14: next_listptr_offset (readelf.c:4939)
==19867== by 0x41EC14: print_debug_loc_section (readelf.c:9247)
==19867== by 0x4122D8: print_debug (readelf.c:11075)
==19867== by 0x415610: process_elf_file (readelf.c:980)
==19867== by 0x41631C: process_dwflmod (readelf.c:744)
==19867== by 0x4E62020: dwfl_getmodules (dwfl_getmodules.c:86)
==19867== by 0x40883B: process_file (readelf.c:852)
==19867== by 0x4044C3: main (readelf.c:338)
==19867== If you believe this happened as a result of a stack
==19867== overflow in your program's main thread (unlikely but
==19867== possible), you can try to increase the size of the
==19867== main thread stack using the --main-stacksize= flag.
==19867== The main thread stack size used in this run was 8388608.
--
You are receiving this mail because:
You are on the CC list for the bug.
