From c33568d2c108478c25fe9959b5ce9d25b97efa6c Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Fri, 25 Oct 2024 06:14:03 +0200 Subject: [PATCH] [gdb/testsuite] Fix gdb.cp/exceptprint.exp with check-read1 Fix test-case gdb.cp/exceptprint.exp with make target check-read1 by limiting the output of skip_libstdcxx_probe_tests_prompt by making the used command more precise: using "info probes stap libstdcxx" instead of "info probes". Tested on x86_64-linux. --- gdb/testsuite/lib/gdb.exp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index a3aaa5cecb0..a438a101fc9 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -5066,7 +5066,8 @@ proc skip_unwinder_tests {} { proc skip_libstdcxx_probe_tests_prompt { prompt_regexp } { set supported 0 - gdb_test_multiple "info probe" "check for stap probe in libstdc++" \ + gdb_test_multiple "info probes stap libstdcxx" \ + "check for stap probe in libstdc++" \ -prompt "$prompt_regexp" { -re ".*libstdcxx.*catch.*\r\n$prompt_regexp" { set supported 1 -- 2.39.5