]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commitdiff
gdb, btrace: simplify gdb.btrace/multi-inferior.exp
authorMarkus Metzger <markus.t.metzger@intel.com>
Thu, 22 Feb 2024 10:32:11 +0000 (10:32 +0000)
committerMarkus Metzger <markus.t.metzger@intel.com>
Mon, 26 May 2025 07:01:14 +0000 (07:01 +0000)
We don't really need three inferiors to test multi-inferior recording.
We don't really need to start recording on the second inferior first.
We don't really need to check info record before starting recording.
If we were recording, there would be output, causing a fail.

This just complicates the test when there is something to debug.

gdb/testsuite/gdb.btrace/multi-inferior.exp

index ed2acb2520dce1dd7592258fbed9f4e90b597634..0dc866729c9b66d99a0246cc59a8c6f2423671f5 100644 (file)
@@ -37,6 +37,8 @@ with_test_prefix "inferior 1" {
     if ![runto_main] {
        return -1
     }
+
+    gdb_test_no_output "record btrace"
 }
 
 with_test_prefix "inferior 2" {
@@ -48,25 +50,5 @@ with_test_prefix "inferior 2" {
        return -1
     }
 
-    gdb_test_no_output "record btrace" "record btrace"
-}
-
-with_test_prefix "inferior 1" {
-    gdb_test "inferior 1" "Switching to inferior 1.*"
-
-    gdb_test "info record" "No recording is currently active\\."
-    gdb_test_no_output "record btrace" "record btrace"
-}
-
-with_test_prefix "inferior 3" {
-    gdb_test "add-inferior -exec ${host_binfile}" "Added inferior 3.*" \
-       "add third inferior"
-    gdb_test "inferior 3" "Switching to inferior 3.*"
-
-    if ![runto_main] {
-       return -1
-    }
-
-    gdb_test "info record" "No recording is currently active\\."
-    gdb_test_no_output "record btrace" "record btrace"
+    gdb_test_no_output "record btrace"
 }