From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/30072] FAIL: run-addr2line-C-test.sh
Date: Fri, 03 Feb 2023 10:06:53 +0000 [thread overview]
Message-ID: <bug-30072-10460-6vgS00qngb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30072-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30072
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Martin Liska from comment #0)
> Created attachment 14650 [details]
> Build log
>
> The test is pretty new and fails with:
>
> [ 30s] FAIL: run-addr2line-C-test.sh
> [ 30s] =============================
> [ 30s]
> [ 30s] --- addr2line.out 2023-02-03 08:59:30.572855287 +0000
> [ 30s] +++ - 2023-02-03 08:59:30.576315349 +0000
> [ 30s] @@ -8,12 +8,12 @@
> [ 30s] (inlined by) baz at /tmp/x.cpp:20
> [ 30s] 0x00000000000005e0: foobar at /tmp/x.cpp:5
> [ 30s] (inlined by) bar at /tmp/x.cpp:15
> [ 30s] - (inlined by) _Z3foov at /tmp/x.cpp:25
> [ 30s] + (inlined by) foo() at /tmp/x.cpp:25
> [ 30s] 0x00000000000005e1: fubar at /tmp/x.cpp:10
> [ 30s] (inlined by) baz at /tmp/x.cpp:20
> [ 30s] - (inlined by) _Z3foov at /tmp/x.cpp:26
> [ 30s] -0x00000000000005f0: _Z2fuv at /tmp/x.cpp:31
> [ 30s] + (inlined by) foo() at /tmp/x.cpp:26
> [ 30s] +0x00000000000005f0: fu() at /tmp/x.cpp:31
> [ 30s] 0x00000000000005f1: fubar at /tmp/x.cpp:10
> [ 30s] - (inlined by) _Z2fuv at /tmp/x.cpp:32
> [ 30s] + (inlined by) fu() at /tmp/x.cpp:32
> [ 30s] 0x00000000000005f2: foobar at /tmp/x.cpp:5
> [ 30s] - (inlined by) _Z2fuv at /tmp/x.cpp:33
> [ 30s] + (inlined by) fu() at /tmp/x.cpp:33
> [ 30s] FAIL run-addr2line-C-test.sh (exit status: 1)
> [ 30s]
> [ 30s] FAIL: run-addr2line-i-test.sh
> [ 30s] =============================
> [ 30s]
> [ 30s] --- addr2line.out 2023-02-03 08:59:30.612856288 +0000
> [ 30s] +++ - 2023-02-03 08:59:30.615130217 +0000
> [ 30s] @@ -1,6 +1,6 @@
> [ 30s] -_Z6foobari at /tmp/x.cpp:4:14
> [ 30s] - (inlined by) _Z3fooi at /tmp/x.cpp:22:16
> [ 30s] - (inlined by) _Z2fui at /tmp/x.cpp:27:13
> [ 30s] -_Z5fubari at /tmp/x.cpp:10:14
> [ 30s] - (inlined by) _Z3bari at /tmp/x.cpp:16:15
> [ 30s] - (inlined by) _Z2fui at /tmp/x.cpp:27:24
> [ 30s] +foobar(int) at /tmp/x.cpp:4:14
> [ 30s] + (inlined by) foo(int) at /tmp/x.cpp:22:16
> [ 30s] + (inlined by) fu(int) at /tmp/x.cpp:27:13
> [ 30s] +fubar(int) at /tmp/x.cpp:10:14
> [ 30s] + (inlined by) bar(int) at /tmp/x.cpp:16:15
> [ 30s] + (inlined by) fu(int) at /tmp/x.cpp:27:24
> [ 30s] FAIL run-addr2line-i-test.sh (exit status: 1)
>
> So somehow the output is demangled, but the test does not expected it.
It looks like the other way around (but the test-suite.log is confusing).
Could you check whether configure detected DEMANGLE support?
libstdc++ demangle support : yes
If not, then the fix would be:
diff --git a/tests/run-addr2line-C-test.sh b/tests/run-addr2line-C-test.sh
index 8c63d78d..1780157d 100755
--- a/tests/run-addr2line-C-test.sh
+++ b/tests/run-addr2line-C-test.sh
@@ -18,6 +18,11 @@
. $srcdir/test-subr.sh
+if test -n "$ELFUTILS_DISABLE_DEMANGLE"; then
+ echo "demangler unsupported"
+ exit 77
+fi
+
# See run-addr2line-i-test.sh
testfiles testfile-inlines
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-03 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:01 [Bug tools/30072] New: " mliska at suse dot cz
2023-02-03 10:06 ` mark at klomp dot org [this message]
2023-02-03 12:36 ` [Bug tools/30072] " mliska at suse dot cz
2023-02-03 12:46 ` mark at klomp dot org
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-30072-10460-6vgS00qngb@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).