A retry build has been detected on builder elfutils-debian-amd64 while building
elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/52/builds/350
Build state: worker not available
Revision: (unknown)
Worker: bb2-2
Build Reason: (unknown)
Blamelist: Aar
A retry build has been detected on builder elfutils-debian-amd64 while building
elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/52/builds/348
Build state: worker not available
Revision: (unknown)
Worker: bb3
Build Reason: (unknown)
Blamelist: Aaron
A new failure has been detected on builder elfutils-fedora-x86_64 while
building elfutils.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/59/builds/348
Build state: failed test (failure)
Revision: 39e962f063b5e8b9c602017c8bc79f03f31873bb
Worker: bbo1-2
Buil
Signed-off-by: Aaron Merey
---
tests/run-sysroot.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/run-sysroot.sh b/tests/run-sysroot.sh
index cfdc51e9..0bbd1aa4 100755
--- a/tests/run-sysroot.sh
+++ b/tests/run-sysroot.sh
@@ -31,6 +31,8 @@ testrun "${abs_top_builddir}"/src/stack --c
run-sysroot.sh checks whether a backtrace generated by eu-stack contains
symbol names found in binaries under a test sysroot. Two frames in
the backtrace contain symbol names that must be read from .gnu_debugdata.
However this section can only be read if elfutils was built with LZMA
support. If
On Thu, Jul 11, 2024 at 04:16:25PM -0400, Frank Ch. Eigler wrote:
> Hi, Omar -
>
> Thanks. I wish this sort of amazing kludge weren't necessary, but
> given that it helps, so be it.
>
> I'd like to commend you on the effort needed to match your code up
> with the stylistic idiosyncracies of the
elf_memory open mode recently changed from ELF_C_READ to
ELF_C_READ_MMAP. This broken dwfl_report_offline_memory that changes
mode to ELF_C_READ_MMAP_PRIVATE to be compatible with subsequent
elf_begin on embedded ELF files.
The proper implementation of dwfl_report_offline_memory doesn't change
ope
Hi, Omar -
Thanks. I wish this sort of amazing kludge weren't necessary, but
given that it helps, so be it.
I'd like to commend you on the effort needed to match your code up
with the stylistic idiosyncracies of the debuginfod c++ code. It
looks just like the other code. My only reservation is