From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/28190] FAIL: run-backtrace-native.sh with glibc 2.34
Date: Thu, 05 Aug 2021 11:06:42 +0000 [thread overview]
Message-ID: <bug-28190-10460-oZw3IQOB6p@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28190-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28190
--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to richard.purdie from comment #4)
> I tested the patch, thanks. This worked on our x86_64 target tests but not
> on our aarch64 ones:
>
> case 0: expected symname 'raise' got '__pthread_kill_internal'
Thanks for testing. Of course it was too optimistic to assume all arches would
use the same naming convention. But good to see the error message now says what
the actual symname was.
Second try at a fix:
https://sourceware.org/pipermail/elfutils-devel/2021q3/004019.html
This time actually tries against a couple of different arches on Fedora rawhide
which also just got glibc 2.35.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-08-05 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 14:32 [Bug libelf/28190] New: " mliska at suse dot cz
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 [this message]
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-oZw3IQOB6p@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).