[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.

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index a3aaa5cecb04a338faaf4f146fe1bda018852bef..a438a101fc9cdfed2916e7c7643405a4a1c4cce3 100644 (file)
--- 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