Re: elfutils 0.175 released
On Tue, 2018-11-20 at 00:43 +0100, Kurt Roeckx wrote:
> On Fri, Nov 16, 2018 at 02:00:46PM +0100, Mark Wielaard wrote:
> > ELFUTILS 0.175 - http://elfutils.org/
> >
> > A new release of elfutils is available at:
> > ftp://sourceware.org/pub/elfutils/0.175/
> > or https://sourceware.org/elfutils/ftp/0.175/
>
> I'm gettings errors on riscv64:
>
https://buildd.debian.org/status/fetch.php?pkg=elfutils&arch=riscv64&ver=0.175-1&stamp=1542669684&raw=0
The riscv backend is fairly new. I don't have access to a riscv setup,
so cannot easily check myself. I have CCed Andreas, who wrote the port
and might be able to diagnose what is going on.
The first failure is for the location description of a return value,
which is kind of expected since riscv doesn't have a
return_value_location backend function yet.
The other 3 failures are all for the self-tests doing unwinding and
look like either DWARF and/or .eh_frame information is missing.
FAIL: run-native-test.sh
/<>/tests/funcretval: dwfl_module_return_value_location:
cannot handle DWARF type description
FAIL: run-backtrace-native.sh
=
0x200x219000/lib/riscv64-linux-gnu/ld-2.27.so
0x21a0000x21c000[vdso: 883]
0x2220000x237000/lib/riscv64-linux-gnu/libpthread-
2.27.so
0x23b0000x2000144000/lib/riscv64-linux-gnu/libc-2.27.so
0x2aa0000x2ae000/<>/tests/backtrace-child
TID 883:
# 0 0x230e26raise
TID 884:
# 0 0x230e26raise
/<>/tests/backtrace: dwfl_thread_getframes: No DWARF
information found
/<>/tests/backtrace: dwfl_thread_getframes: No DWARF
information found
backtrace: backtrace.c:81: callback_verify: Assertion `seen_main'
failed.
./test-subr.sh: line 84: 880
Aborted LD_LIBRARY_PATH="${built_library_path}${LD_LIBR
ARY_PATH:+:}$LD_LIBRARY_PATH" $VALGRIND_CMD "$@"
backtrace-child: no main
FAIL run-backtrace-native.sh (exit status: 1)
FAIL: run-backtrace-dwarf.sh
0x2a3d12raise
/<>/tests/backtrace-dwarf: dwfl_thread_getframes: No DWARF
information found
dwarf: no main
FAIL run-backtrace-dwarf.sh (exit status: 1)
FAIL: run-backtrace-native-core.sh
==
backtrace: backtrace.c:111: callback_verify: Assertion `symname &&
strcmp (symname, "raise") == 0' failed.
./test-subr.sh: line 84: 975
Aborted LD_LIBRARY_PATH="${built_library_path}${LD_LIBR
ARY_PATH:+:}$LD_LIBRARY_PATH" $VALGRIND_CMD "$@"
backtrace-child-core.965: no main
rmdir: failed to remove 'test-944': Directory not empty
FAIL run-backtrace-native-core.sh (exit status: 1)
Re: elfutils 0.175 released
The riscv port is still work in progress. Patches welcome to implement the missing bits. The backtrace-dwarf test doesn't fail for me, btw. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
[Bug general/23901] New: run-backtrace-native-core returns error isntead of skip
https://sourceware.org/bugzilla/show_bug.cgi?id=23901 Bug ID: 23901 Summary: run-backtrace-native-core returns error isntead of skip Product: elfutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: general Assignee: unassigned at sourceware dot org Reporter: kurt at roeckx dot be CC: elfutils-devel at sourceware dot org Target Milestone: --- On MIPS I get: FAIL: run-backtrace-native-core.sh == /<>/tests/backtrace: dwfl_pid: Unwinding not supported for this architecture backtrace-child-core.9086: arch not supported rmdir: failed to remove 'test-9078': Directory not empty FAIL run-backtrace-native-core.sh (exit status: 1) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/23901] run-backtrace-native-core returns error isntead of skip
https://sourceware.org/bugzilla/show_bug.cgi?id=23901 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org --- Comment #1 from Mark Wielaard --- That is indeed weird. It should exit 77 on that message. But it seems there is something left in that test-9078 test subdir. That would indeed make it fail. What is in that dir? Note that there is no MIPS backend support, so failures are expected. It might be that you have local debian patches that provide some MIPS support which might explain the issue. It would be nice to have a MIPS arch expert submit these patches upstream to get official MIPS support for elfutils. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/23901] run-backtrace-native-core returns error isntead of skip
https://sourceware.org/bugzilla/show_bug.cgi?id=23901 --- Comment #2 from Kurt Roeckx --- Yes, I've had this mips patch written in 2006. But I've been unable to contact the author of that. It has had various fixes since, but the current version also has other issues, see: https://buildd.debian.org/status/fetch.php?pkg=elfutils&arch=mips&ver=0.175-1&stamp=1542667301&raw=0 Anyway, the directory contains: -rw--- 1 kroeckx kroeckx 8790016 Nov 20 19:23 core.10371 -rw-r--r-- 1 kroeckx kroeckx 0 Nov 20 19:23 core.10371.bt -rw-r--r-- 1 kroeckx kroeckx 102 Nov 20 19:23 core.10371.err -- You are receiving this mail because: You are on the CC list for the bug.
[Bug backends/23902] New: varlocs dwarf_cfi_addrframe: unknown error
https://sourceware.org/bugzilla/show_bug.cgi?id=23902 Bug ID: 23902 Summary: varlocs dwarf_cfi_addrframe: unknown error Product: elfutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: backends Assignee: unassigned at sourceware dot org Reporter: kurt at roeckx dot be CC: elfutils-devel at sourceware dot org Target Milestone: --- On at least mips, alpha and hppa, I'm getting something like: /<>/tests/varlocs: dwarf_cfi_addrframe 0x120002540: unknown error *** failure in /<>/tests/varlocs -e /<>/src/addr2line Logs can be found at: https://buildd.debian.org/status/fetch.php?pkg=elfutils&arch=alpha&ver=0.175-1&stamp=1542672225&raw=0 https://buildd.debian.org/status/fetch.php?pkg=elfutils&arch=mips&ver=0.175-1&stamp=1542667301&raw=0 https://buildd.debian.org/status/fetch.php?pkg=elfutils&arch=hppa&ver=0.175-1&stamp=1542666561&raw=0 The mips and hppa backend are patches that only exist in Debian, but alpha seems to be part of upstream. Is this some indication of missing functionality? Any suggestion where to look? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libelf/23903] New: Uses linux specifc mremap
https://sourceware.org/bugzilla/show_bug.cgi?id=23903 Bug ID: 23903 Summary: Uses linux specifc mremap Product: elfutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: libelf Assignee: unassigned at sourceware dot org Reporter: kurt at roeckx dot be CC: elfutils-devel at sourceware dot org Target Milestone: --- In Debian's kfreebsd ports, I'm getting: /usr/bin/ld: libelf_pic.a(elf_update.os): in function `write_file': ./libelf/elf_update.c:109: undefined reference to `mremap' -- You are receiving this mail because: You are on the CC list for the bug.
