From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/28190] New: FAIL: run-backtrace-native.sh with glibc 2.34
Date: Wed, 04 Aug 2021 14:32:32 +0000 [thread overview]
Message-ID: <bug-28190-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28190
Bug ID: 28190
Summary: FAIL: run-backtrace-native.sh with glibc 2.34
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libelf
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
I see the following failure:
[ 349s] FAIL: run-backtrace-native.sh
[ 349s] =============================
[ 349s]
[ 349s] backtrace: backtrace.c:111: callback_verify: Assertion `symname &&
strcmp (symname, "raise") == 0' failed.
[ 349s] ./test-subr.sh: line 84: 13043 Aborted
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
[ 349s] backtrace-child: no main
[ 349s] FAIL run-backtrace-native.sh (exit status: 1)
If I see correctly, symname is pthread_kill@GLIBC_2.2.5 for frameno == 0.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-08-04 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 14:32 mliska at suse dot cz [this message]
2021-08-04 17:13 ` [Bug libelf/28190] " richard.purdie at linuxfoundation dot org
2021-08-04 18:56 ` mark at klomp dot org
2021-08-04 19:04 ` mark at klomp dot org
2021-08-05 7:45 ` richard.purdie at linuxfoundation dot org
2021-08-05 11:06 ` mark at klomp dot org
2021-08-05 16:50 ` richard.purdie at linuxfoundation dot org
2021-08-05 17:09 ` mark at klomp dot org
2021-08-25 8:47 ` fweimer at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28190-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).