public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <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 15:31:21 +0000	[thread overview]
Message-ID: <bug-29176-10460-G2NgB6rSr6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29176-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29176

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
(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.

  reply	other threads:[~2022-05-27 15:31 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 ` mark at klomp dot org [this message]
2022-05-27 16:04 ` [Bug general/29176] " evvers at ya dot ru
2022-05-27 17:02 ` evvers at ya dot ru
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-G2NgB6rSr6@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).