From 5ec878132bb39fb43e081dcf53e42aca202b24d9 Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Fri, 29 Jul 2022 16:12:55 +0200 Subject: [PATCH] [gdb/testsuite] Fix gdb.ada/convvar_comp.exp with broken debug info On aarch64-linux I run into this failure with gcc 7.5.0: ... (gdb) print $item.started^M $1 = (-5312, 65535, 4202476)^M (gdb) FAIL: gdb.ada/convvar_comp.exp: print $item.started ... The test-case expects (0, 0, 0), but we're getting another value due to incorrect location information. Work around this by: - first printing the value, and then - verifying that the convenience variable matches the printed value. I've verified that the test-case still checks what it should by disabling the fix from commit cc0e770c0d0 ("memory error printing component of record from convenience variable") and observing the test-case fail. Tested on x86_64-linux and aarch64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29420 --- gdb/testsuite/gdb.ada/convvar_comp.exp | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/gdb.ada/convvar_comp.exp b/gdb/testsuite/gdb.ada/convvar_comp.exp index ebc2659aeaa..1923bd785c7 100644 --- a/gdb/testsuite/gdb.ada/convvar_comp.exp +++ b/gdb/testsuite/gdb.ada/convvar_comp.exp @@ -30,7 +30,15 @@ if ![runto "break_me" ] then { return } +set val "" +gdb_test_multiple "print item.started" "" { + -re -wrap " = \\((.*)\\)" { + set val $expect_out(1,string) + pass $gdb_test_name + } +} + gdb_test_no_output "set variable \$item := item" gdb_test "print \$item.started" \ - " = \\(0, 0, 0\\)" + " = \\($val\\)" -- 2.30.2