From 70ff156a27223692c8927ade91220f26541e6f3c Mon Sep 17 00:00:00 2001 From: Simon Marchi Date: Fri, 21 Nov 2025 15:13:58 -0500 Subject: [PATCH] gdb/testsuite/dwarf: ensure build_executable_and_dwo_files calls untested in all failure paths There are some paths of build_executable_and_dwo_files that return -1 without calling "untested". As a result, tests such as gdb.dwarf2/fission-absolute-dwo.exp would exit without leaving a trace. Add some untested calls to fix that. Change-Id: I2e632b5b44b11b4beb39791316f1203f9a12bf4f Approved-By: Tom Tromey --- gdb/testsuite/lib/dwarf.exp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gdb/testsuite/lib/dwarf.exp b/gdb/testsuite/lib/dwarf.exp index 6e87d8fba9b..dc9d69518c5 100644 --- a/gdb/testsuite/lib/dwarf.exp +++ b/gdb/testsuite/lib/dwarf.exp @@ -116,17 +116,20 @@ proc build_executable_and_dwo_files { testname executable options args } { # Currently don't support compiling thread based tests here. # If this is required then look to build_executable_from_specs # for inspiration. + untested "option not supported" return -1 } if {[lsearch -exact $options rust] != -1} { # Currently don't support compiling rust tests here. If this # is required then look to build_executable_from_specs for # inspiration. + untested "rust not supported" return -1 } # Must be run on local host due to use of objcopy. if {[is_remote host]} { + untested "using remote host" return -1 } -- 2.47.3