From: "evvers at ya dot ru" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29176] run-backtrace-native-biarch.sh seems to fail on Ubuntu Jammy
Date: Fri, 27 May 2022 17:02:15 +0000 [thread overview]
Message-ID: <bug-29176-10460-vSzHXO3s4S@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29176-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29176
--- Comment #3 from Evgeny Vereshchagin <evvers at ya dot ru> ---
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.
next prev parent reply other threads:[~2022-05-27 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 21:14 [Bug general/29176] New: " evvers at ya dot ru
2022-05-27 15:31 ` [Bug general/29176] " mark at klomp dot org
2022-05-27 16:04 ` evvers at ya dot ru
2022-05-27 17:02 ` evvers at ya dot ru [this message]
2022-05-27 20:58 ` evvers at ya dot ru
2022-05-28 0:01 ` mark at klomp dot org
2022-05-28 0:22 ` evvers at ya dot ru
2022-05-31 14:14 ` fantasquex at gmail dot com
2022-09-13 10:06 ` jbglaw@lug-owl.de
2023-03-04 11:24 ` jbglaw@lug-owl.de
2023-03-04 20:35 ` mark at klomp dot org
2023-03-04 21:40 ` mark at klomp dot org
2023-03-05 9:34 ` jbglaw@lug-owl.de
2023-03-05 12:16 ` mark at klomp dot org
2023-11-14 11:56 ` bschnzl at cotse dot net
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-29176-10460-vSzHXO3s4S@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).