[Bug,tools/30072] FAIL: run-addr2line-C-test.sh

Message ID bug-30072-10460-6vgS00qngb@http.sourceware.org/bugzilla/
State Committed
Headers
Series [Bug,tools/30072] FAIL: run-addr2line-C-test.sh |

Commit Message

dodji at seketeli dot org Feb. 3, 2023, 10:06 a.m. UTC
  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:
  

Patch

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