From a03c03f84ac331a1ae03fbf1d7e53001935e45be Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Tue, 22 Oct 2024 09:23:26 +0200 Subject: [gdb/testsuite] Handle maint set dwarf synchronous off default I ran the testsuite with a patch setting dwarf_synchronous to false by default, and ran into FAILs in test-cases gdb.dwarf2/dw2-inter-cu-error.exp and gdb.dwarf2/dw2-inter-cu-error-2.exp, because the expected DWARF errors did not show up as a result of the file command. Fix this by forcing "maint set dwarf synchronous on". Add the same in gdb.base/index-cache.exp, where this is also required. Tested on aarch64-linux. --- gdb/testsuite/gdb.dwarf2/dw2-inter-cu-error.exp | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'gdb/testsuite/gdb.dwarf2/dw2-inter-cu-error.exp') diff --git a/gdb/testsuite/gdb.dwarf2/dw2-inter-cu-error.exp b/gdb/testsuite/gdb.dwarf2/dw2-inter-cu-error.exp index 92ffcae..5de2790 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-inter-cu-error.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-inter-cu-error.exp @@ -41,11 +41,17 @@ Dwarf::assemble $asm_file { } } -if [prepare_for_testing "failed to prepare" $testfile \ +if [build_executable "failed to prepare" $testfile \ [list $asm_file $srcfile] {nodebug}] { return -1 } +clean_restart + +gdb_test_no_output "maint set dwarf synchronous on" + +gdb_load $binfile + # Verify that GDB notices the null DIE. gdb_assert { [regexp "DWARF Error: Unexpected null DIE" $gdb_file_cmd_msg] } \ "Null DIE error missing" -- cgit v1.1