[Bug general/29180] run-debuginfod-fd-prefetch-caches.sh seems to fail on Ubuntu Focal when elfutils is built with --enable-gcov
https://sourceware.org/bugzilla/show_bug.cgi?id=29180 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org Assignee|unassigned at sourceware dot org |nsanci at redhat dot com --- Comment #1 from Mark Wielaard --- Noah just posted a patch to make that test do something. I assumed it was a dummy test before. Could you take a look at his proposed patch to see if that resolves the issue for you? https://sourceware.org/pipermail/elfutils-devel/2022q2/005090.html -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/25368] handle native golang buildids
https://sourceware.org/bugzilla/show_bug.cgi?id=25368 Noah Sanci changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED CC||nsanci at redhat dot com --- Comment #1 from Noah Sanci --- Debuginfod can scan rpms including golang executables, debuginfo, and source and serve them so long as the golang binary has an associate gnu build. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/28325] create new debuginfod.service.8 man page
https://sourceware.org/bugzilla/show_bug.cgi?id=28325 Noah Sanci changed: What|Removed |Added CC||nsanci at redhat dot com Assignee|unassigned at sourceware dot org |nsanci at redhat dot com -- You are receiving this mail because: You are on the CC list for the bug.
Re: [PATCH] libdwfl: Update docs and nonnull attributes for dwfl_module_addrinfo
Hi, On Sun, 2022-05-15 at 22:00 +0200, Mark Wielaard wrote: > Make clear that both the offset and sym arguments cannot be NULL. > > https://bugzilla.redhat.com/show_bug.cgi?id=1986555 I didn't get feedback on the actual wording, but I think this is better than we had. So pushed. Cheers, Mark
[Bug debuginfod/25368] handle native golang buildids
https://sourceware.org/bugzilla/show_bug.cgi?id=25368 --- Comment #2 from Noah Sanci --- (In reply to Noah Sanci from comment #1) > Debuginfod can scan rpms including golang executables, debuginfo, and source > and serve them so long as the golang binary has an associate gnu build. Debuginfod functions with golang binaries so long as the binary has an associated .note.gnu.build-id -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
https://sourceware.org/bugzilla/show_bug.cgi?id=29176
Mark Wielaard changed:
What|Removed |Added
CC||mark at klomp dot org
--- Comment #1 from Mark Wielaard ---
(In reply to Evgeny Vereshchagin from comment #0)
> I tried to switch to Ubuntu Jammy in
> https://github.com/evverx/elfutils/pull/83 and the test started failing
> there with
> ```
> FAIL: run-backtrace-native-biarch.sh
>
>
> case 0: expected symname 'raise' got '(null)'
> ./test-subr.sh: line 84: 23451 Aborted (core dumped)
> LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
> $VALGRIND_CMD "$@"
> backtrace-child-biarch: no main
> FAIL run-backtrace-native-biarch.sh (exit status: 1)
>
> ```
> It still passes on Ubuntu Focal.
>
> FWIW switching to Ubuntu Jammy somehow "fixed"
> run-debuginfod-fd-prefetch-caches.sh (which appears to be flaky on Ubuntu
> Focal and fails more or less consistently when elfutils is built with
> --enable-gcov: https://github.com/evverx/elfutils/runs/6577995202)
Note that github makes log non-public by default, so it is hard to see what is
going on.
Do you have any more information on what changed between "Focal" and "Jammy",
glibc upgrade? some system settings, gcc upgrade? That might explain what you
are seeing?
Basically the testcase says it cannot find the name associated with the frame.
It is NULL while it is expecting the symbol name "raise".
This is a somewhat gnarly test. Best might be to add some extra printfs to
tests/backtrace.c (callback_verify) printing the frameno and framename found to
see what is going on.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug general/29180] run-debuginfod-fd-prefetch-caches.sh seems to fail on Ubuntu Focal when elfutils is built with --enable-gcov
https://sourceware.org/bugzilla/show_bug.cgi?id=29180 --- Comment #2 from Evgeny Vereshchagin --- With that patch applied the test passed in https://github.com/evverx/elfutils/pull/86 and according to https://coveralls.io/builds/49520251 the coverage of debuginfod.cxx went up a little. `git am` complained about trailing whitespaces ``` Applying: PR28577: Make run-debuginfod-fd-prefetch-caches.sh test something .git/rebase-apply/patch:75: trailing whitespace. kill -USR1 $PID1 .git/rebase-apply/patch:115: trailing whitespace. fi warning: 2 lines add whitespace errors. ``` -- You are receiving this mail because: You are on the CC list for the bug.
☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
A new failure has been detected on builder elfutils-centos-x86_64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/39/builds/31 Build state: failed test (failure) Revision: b8713b3fd0617415c76df8c9da70f8e2f26d3134 Worker: centos-x86_64 Build Reason: (unknown) Blamelist: Mark Wielaard Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/4/logs/stdio - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/6/logs/stdio - warnings (2): https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/6/logs/warnings__2_ - 7: make check ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/8/logs/stdio - 9: fetch ['tests/*.trs', 'tests/*.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/9/logs/stdio - 10: fetch ['elfutils-*/_build/sub/tests/*.trs', 'elfut ( skipped ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/10/logs/stdio - 11: fetch ['config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/11/logs/stdio - 12: fetch ['elfutils-*/_build/sub/config.log'] ( skipped ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/12/logs/stdio - 13: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/13/logs/stdio - 14: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/14/logs/stdio - 15: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/15/logs/stdio - 16: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/16/logs/stdio
[Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
https://sourceware.org/bugzilla/show_bug.cgi?id=29176 --- Comment #2 from Evgeny Vereshchagin --- > Do you have any more information on what changed between "Focal" and "Jammy", > glibc upgrade? some system settings, gcc upgrade? That might explain what you > are seeing? I think everything was upgraded there. As far as I can see gcc-9.4.0 was replaced with gcc-11.2.0 and glibc was upgraded from 2.31-0ubuntu9.7 to 2.35-0ubuntu3. > Best might be to add some extra printfs to tests/backtrace.c > (callback_verify) printing the frameno and framename found to see what is > going on. I'll try to do that. -- You are receiving this mail because: You are on the CC list for the bug.
Re: [Bug debuginfod/28577] Make run-...-fd-prefetch-caches.sh test something
Hi Noah,
On Wed, 2022-05-25 at 14:44 -0400, Noah Sanci via Elfutils-devel wrote:
> PR28577: Make run-debuginfod-fd-prefetch-caches.sh test
> something
>
> Update to the run-debuginfod-fd-prefetch to make the test more sound.
Thanks. And according to Evgeny this makes the test pass for him:
https://sourceware.org/bugzilla/show_bug.cgi?id=29180#c2
But I find it a little hard to review, it would have been helpful to
get a bit more comments/documentation what exactly is being tested now.
> diff --git a/tests/run-debuginfod-fd-prefetch-caches.sh b/tests/run-
> debuginfod-fd-prefetch-caches.sh
> index 66a7a083..50ffc4ac 100755
> --- a/tests/run-debuginfod-fd-prefetch-caches.sh
> +++ b/tests/run-debuginfod-fd-prefetch-caches.sh
> @@ -21,22 +21,22 @@
> # for test case debugging, uncomment:
> set -x
> unset VALGRIND_CMD
> +mkdir R Z
OK, some boilerplate.
> -mkdir R
> -cp -rvp ${abs_srcdir}/debuginfod-rpms R
> -if [ "$zstd" = "false" ]; then # nuke the zstd fedora 31 ones
> -rm -vrf R/debuginfod-rpms/fedora31
> -fi
This gets moved to below.
> -FDCACHE_MBS=$((1/1024/1024))
> +FDCACHE_MBS=1
> FDCACHE_FDS=1
> -PREFETCH_MBS=$((1/1024/1024))
> -PREFETCH_FDS=2
> +PREFETCH_MBS=1
> +PREFETCH_FDS=1
> PREFETCH=1
OK, new presets.
> # This variable is essential and ensures no time-race for claiming
> ports occurs
> # set base to a unique multiple of 100 not used in any other 'run-
> debuginfod-*' test
> base=8800
> get_ports
> +cp -rvp ${abs_srcdir}/debuginfod-rpms R
> +if [ "$zstd" = "false" ]; then # nuke the zstd fedora 31 ones
> +rm -vrf R/debuginfod-rpms/fedora31
> +fi
> +cp -rvp ${abs_srcdir}/debuginfod-tars Z
OK, put rpms under R, tars under Z.
> DB=${PWD}/.debuginfod_tmp.sqlite
> tempfiles $DB
> @@ -47,88 +47,68 @@ export DEBUGINFOD_CACHE_PATH=${PWD}/.client_cache
> ##
> rm -rf $DEBUGINFOD_CACHE_PATH
> rm -rf $DB
> +
> # Set mb values to ensure the caches certainly have enough space
> # To store the test files
> env LD_LIBRARY_PATH=$ldpath DEBUGINFOD_URLS=
> ${abs_builddir}/../debuginfod/debuginfod $VERBOSE -p $PORT1 -d $DB \
> ---fdcache-fds=$FDCACHE_FDS --fdcache-prefetch-fds=$PREFETCH_FDS
> --fdcache-mintmp 0 -v -g 0 -t 0 -R R \
> ---fdcache-mbs=50 --fdcache-prefetch-mbs=50 \
> ---fdcache-prefetch=$PREFETCH > vlog$PORT1 2>&1 &
> +--fdcache-fds=$FDCACHE_FDS --fdcache-prefetch-fds=$PREFETCH_FDS -v
> -g 0 -t 0 -R R \
> +-Z .tar.bz2=bzcat Z --fdcache-mbs=50 --fdcache-prefetch-mbs=100 \
> +--fdcache-prefetch=$PREFETCH -F > vlog$PORT1 2>&1 &
Now run with --fdcache-fds=1 --fdcache-mbs=50 and
-fdcache-prefetch-fds=1 fdcache-prefetch=1 -fdcache-prefetch-mbs=100
It is these last 3 we want to test.
> PID1=$!
> tempfiles vlog$PORT1
> errfiles vlog$PORT1
> +
> # Server must become ready
> wait_ready $PORT1 'ready' 1
>
> -cp -rvp ${abs_srcdir}/debuginfod-rpms R
> -if [ "$zstd" = "false" ]; then # nuke the zstd fedora 31 ones
> -rm -vrf R/debuginfod-rpms/fedora31
> -fi
> kill -USR1 $PID1
> wait_ready $PORT1 'thread_work_total{role="traverse"}' 1
> +wait_ready $PORT1 'thread_work_pending{role="scan"}' 0
> +wait_ready $PORT1 'thread_busy{role="scan"}' 0
OK, boilerplate to wait for initial scan.
> # All rpms need to be in the index, except the dummy permission-000 one
> rpms=$(find R -name \*rpm | grep -v nothing | wc -l)
> wait_ready $PORT1 'scanned_files_total{source=".rpm archive"}' $rpms
> -kill -USR1 $PID1 # two hits of SIGUSR1 may be needed to resolve
> .debug->dwz->srefs
> -# Wait till both files are in the index and scan/index fully finished
> +kill -USR1 $PID1
> wait_ready $PORT1 'thread_work_total{role="traverse"}' 2
> -export DEBUGINFOD_URLS="http://127.0.0.1:"$PORT1
> +wait_ready $PORT1 'thread_work_pending{role="scan"}' 0
> +wait_ready $PORT1 'thread_busy{role="scan"}' 0
Do another scan and wait for it to be ready.
> -archive_hits=5
> -SHA=f4a1a8062be998ae93b8f1cd744a398c6de6dbb1
> -for i in $archive_hits
> -do
> - archive_test c36708a78618d597dee15d0dc989f093ca5f9120
> /usr/src/debug/hello2-1.0-2.x86_64/hello.c $SHA
> -done
> +export DEBUGINFOD_URLS=http://127.0.0.1:$PORT1/
> +# load prefetch cache
> +testrun ${abs_top_builddir}/debuginfod/debuginfod-find debuginfo
> cee13b2ea505a7f37bd20d271c6bc7e5f8d2dfcb
OK, which particular file is this?
> metrics=$(curl http://127.0.0.1:$PORT1/metrics)
> -regex="fdcache_op_count\{op=\"enqueue\"\}
> ([0-9]+).*fdcache_op_count\{op=\"evict\"\} ([0-9]+).*"
> -enqueue=0
> -if [[ $metrics =~ $regex ]]
> -then
> - enqueue=${BASH_REMATCH[1]}
> - evict=${BASH_REMATCH[2]}
> +regex="fdcache_prefetch_count ([0-9])+"
> +# Check to see if prefetch cache is loaded
> +if [[ $metrics =~ $regex ]]; then
> + if [[ ${BASH_REMATCH[1]} -ne 1 ]]; then
> +err
> + fi
Why the -ne 1 ? What number are we expecting and why?
> else
> - err
> -fi
> -# This is an ad-hoc test than only works when F
[Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
https://sourceware.org/bugzilla/show_bug.cgi?id=29176 --- Comment #3 from Evgeny Vereshchagin --- I added printf and here's what it printed on Ubuntu Jammy: ``` FRAMENO: '0', SYMNAME: '__kernel_vsyscall' FRAMENO: '1', SYMNAME: '' FRAMENO: '2', SYMNAME: 'raise' FRAMENO: '3', SYMNAME: 'main' FRAMENO: '4', SYMNAME: '' FRAMENO: '5', SYMNAME: '__libc_start_main' FRAMENO: '6', SYMNAME: '_start' FRAMENO: '0', SYMNAME: '__kernel_vsyscall' FRAMENO: '1', SYMNAME: '' case 0: expected symname 'raise' got '(null)' ``` On Fedora 35 (where the test passes) I got ``` FRAMENO: '0', SYMNAME: '__kernel_vsyscall' FRAMENO: '1', SYMNAME: '__pthread_kill_implementation' FRAMENO: '2', SYMNAME: 'raise' FRAMENO: '3', SYMNAME: 'main' FRAMENO: '0', SYMNAME: '__kernel_vsyscall' FRAMENO: '1', SYMNAME: '__pthread_kill_implementation' FRAMENO: '2', SYMNAME: 'raise' FRAMENO: '3', SYMNAME: 'sigusr2' FRAMENO: '4', SYMNAME: 'stdarg' FRAMENO: '5', SYMNAME: 'backtracegen' FRAMENO: '6', SYMNAME: 'start' FRAMENO: '7', SYMNAME: 'start_thread' FRAMENO: '8', SYMNAME: '__clone3' FRAMENO: '0', SYMNAME: '' ``` -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
https://sourceware.org/bugzilla/show_bug.cgi?id=29176 Evgeny Vereshchagin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Evgeny Vereshchagin --- Looks like it's possible to make the test pass there by installing libc6-i386-dbgsym (though I'm not sure why the test passes without that package on Focal). Anyway it doesn't seem to be an elfutils issue. I'll go ahead and close it. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
On Fri, May 27, 2022 at 04:02:41PM +, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-centos-x86_64 while
> building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/39/builds/31
>
> Build state: failed test (failure)
> Revision: b8713b3fd0617415c76df8c9da70f8e2f26d3134
> Worker: centos-x86_64
> Build Reason: (unknown)
> Blamelist: Mark Wielaard
>
> Steps:
> [...]
> - 7: make check ( failure )
> Logs:
> - stdio:
> https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/7/logs/stdio
> - test-suite.log:
> https://builder.sourceware.org/buildbot/#builders/39/builds/31/steps/7/logs/test-suite_log
The failure comes from run-debuginfod-federation-metrics.sh, this
part:
# Trigger a flood of requests against the same archive content file.
# Use a file that hasn't been previously extracted in to make it
# likely that even this test debuginfod will experience concurrency
# and impose some "after-you" delays.
(for i in `seq 100`; do
curl -s
http://127.0.0.1:$PORT1/buildid/87c08d12c78174f1082b7c888b3238219b0eb265/executable
>/dev/null &
done;
wait)
curl -s http://127.0.0.1:$PORT1/metrics | grep 'http_responses_after_you.*'
Where the error is:
+ curl -s http://127.0.0.1:9025/metrics
+ grep 'http_responses_after_you.*'
/srv/buildbot/worker/elfutils-centos-x86_64/build/tests/run-debuginfod-federation-metrics.sh:
line 198: 27160 Aborted (core dumped) env
LD_LIBRARY_PATH=$ldpath ${abs_builddir}/../debuginfod/debuginfod $VERBOSE -d
${DB} -F -U -t0 -g0 -p $PORT1 L D F > vlog$PORT1 2>&1
++ err
++ trap - ERR
++ echo ERROR REPORTS
This doesn't really make sense to me. Sadly the test machine doesn't actually
have a core file:
Process 27160 (debuginfod) of user 994 killed by SIGABRT - ignoring (low free
space)
Lets see what happens on a rebuild.
Cheers,
Mark
☺ Buildbot (GNU Toolchain): elfutils - build successful (master)
A restored build has been detected on builder elfutils-centos-x86_64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#builders/39/builds/32 Build state: build successful Revision: b8713b3fd0617415c76df8c9da70f8e2f26d3134 Worker: centos-x86_64 Build Reason: (unknown) Blamelist: Mark Wielaard Steps: - 0: worker_preparation ( success ) - 1: set package name ( success ) - 2: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/2/logs/stdio - 3: autoreconf ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/3/logs/stdio - 4: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/4/logs/stdio - 5: get version ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/5/logs/stdio - property changes: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/5/logs/property_changes - 6: make ( warnings ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/6/logs/stdio - warnings (2): https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/6/logs/warnings__2_ - 7: make check ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/7/logs/stdio - test-suite.log: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/7/logs/test-suite_log - 8: prep ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/8/logs/stdio - 9: fetch ['tests/*.trs', 'tests/*.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/9/logs/stdio - 10: fetch ['elfutils-*/_build/sub/tests/*.trs', 'elfut ( skipped ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/10/logs/stdio - 11: fetch ['config.log'] ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/11/logs/stdio - 12: fetch ['elfutils-*/_build/sub/config.log'] ( skipped ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/12/logs/stdio - 13: pass .bunsen.source.gitname ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/13/logs/stdio - 14: pass .bunsen.source.gitrepo ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/14/logs/stdio - 15: upload to bunsen ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/15/logs/stdio - 16: clean up ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/39/builds/32/steps/16/logs/stdio
[Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
https://sourceware.org/bugzilla/show_bug.cgi?id=29176 Mark Wielaard changed: What|Removed |Added Resolution|INVALID |--- Ever confirmed|0 |1 Last reconfirmed||2022-05-28 Status|RESOLVED|REOPENED --- Comment #5 from Mark Wielaard --- I hope you don't mind me reopening the bug. I would like the testcase to work even without the dbgsym installed. Is the dbgsym package for the main (x86_64) libc6 package also installed? The problem is that the testcase requires all addresses to map to a know symbol name. But what we are really interested in is that we are unwinding through the main or the start_thread symbols. We probably should just skip any unknown/NULL symbols. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
https://sourceware.org/bugzilla/show_bug.cgi?id=29176 --- Comment #6 from Evgeny Vereshchagin --- > Is the dbgsym package for the main (x86_64) libc6 package also installed? As far as I can see libc6-dbg is installed there but even without it when code is compiled without -m32 and aborts backtraces don't contain NULL/unknown symbols: ``` #0 0x77e25a7c in pthread_kill () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x77dd1476 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x77db77f3 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x5161 in main () ``` With -m32 and without the "x32" debug symbols backtraces look like ``` #0 0xf7fc4559 in __kernel_vsyscall () #1 0xf7e10e37 in ?? () from /lib32/libc.so.6 #2 0xf7dc04c5 in raise () from /lib32/libc.so.6 #3 0xf7da93ac in abort () from /lib32/libc.so.6 #4 0x565561b5 in main () ``` > We probably should just skip any unknown/NULL symbols. As far as I understand it should make the test pass even without the debug symbols. -- You are receiving this mail because: You are on the CC list for the bug.
Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Hi -
n-metrics.sh: line 198: 27160 Aborted (core dumped) env
LD_LIBRARY_PATH=$ldpath ${abs_builddir}/../debuginfod/debuginfod $VERBOSE -d
${DB} -F -U -t0 -g0 -p $PORT1 L D F > vlog$PORT1 2>&1
> [...]
> Process 27160 (debuginfod) of user 994 killed by SIGABRT - ignoring (low free
> space)
> Lets see what happens on a rebuild.
Did the machine run out of memory / storage?
- FChE
