* [Bug tools/30072] New: FAIL: run-addr2line-C-test.sh
@ 2023-02-03 9:01 mliska at suse dot cz
2023-02-03 10:06 ` [Bug tools/30072] " mark at klomp dot org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: mliska at suse dot cz @ 2023-02-03 9:01 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=30072
Bug ID: 30072
Summary: FAIL: run-addr2line-C-test.sh
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: elfutils-devel at sourceware dot org, mark at klomp dot org
Target Milestone: ---
Created attachment 14650
--> https://sourceware.org/bugzilla/attachment.cgi?id=14650&action=edit
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug tools/30072] FAIL: run-addr2line-C-test.sh
2023-02-03 9:01 [Bug tools/30072] New: FAIL: run-addr2line-C-test.sh mliska at suse dot cz
@ 2023-02-03 10:06 ` mark at klomp dot org
2023-02-03 12:36 ` mliska at suse dot cz
2023-02-03 12:46 ` mark at klomp dot org
2 siblings, 0 replies; 4+ messages in thread
From: mark at klomp dot org @ 2023-02-03 10:06 UTC (permalink / raw)
To: elfutils-devel
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.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug tools/30072] FAIL: run-addr2line-C-test.sh
2023-02-03 9:01 [Bug tools/30072] New: FAIL: run-addr2line-C-test.sh mliska at suse dot cz
2023-02-03 10:06 ` [Bug tools/30072] " mark at klomp dot org
@ 2023-02-03 12:36 ` mliska at suse dot cz
2023-02-03 12:46 ` mark at klomp dot org
2 siblings, 0 replies; 4+ messages in thread
From: mliska at suse dot cz @ 2023-02-03 12:36 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=30072
--- Comment #2 from Martin Liska <mliska at suse dot cz> ---
> 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
Yes, I really miss it:
configure:8679: checking for __cxa_demangle in -lstdc++
configure:8702: gcc -o conftest -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
-fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects
-Werror=date-time -g -flto=auto -ffat-lto-objects conftest.c -lstdc++ >&5
/usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld:
cannot find -lstdc++: No such file or directory
collect2: error: ld returned 1 exit status
configure:8702: $? = 1
configure: failed program was:
Oh, apparently my spec file has not BuildRequires of the gcc-c++ package.
Adding that, all is green.
>
> 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
This would fix it as well..
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug tools/30072] FAIL: run-addr2line-C-test.sh
2023-02-03 9:01 [Bug tools/30072] New: FAIL: run-addr2line-C-test.sh mliska at suse dot cz
2023-02-03 10:06 ` [Bug tools/30072] " mark at klomp dot org
2023-02-03 12:36 ` mliska at suse dot cz
@ 2023-02-03 12:46 ` mark at klomp dot org
2 siblings, 0 replies; 4+ messages in thread
From: mark at klomp dot org @ 2023-02-03 12:46 UTC (permalink / raw)
To: elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=30072
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
commit dd3c621ff36f73cb26d89a2fd5ea384a5b33334c
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Feb 3 13:44:17 2023 +0100
tests: Check ELFUTILS_DISABLE_DEMANGLE in run-addr2line-C-test.sh
https://sourceware.org/bugzilla/show_bug.cgi?id=30072
Signed-off-by: Mark Wielaard <mark@klomp.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-02-03 12:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-03 9:01 [Bug tools/30072] New: FAIL: run-addr2line-C-test.sh mliska at suse dot cz
2023-02-03 10:06 ` [Bug tools/30072] " mark at klomp dot org
2023-02-03 12:36 ` mliska at suse dot cz
2023-02-03 12:46 ` mark at klomp dot org
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).