[14/27] Use clean_restart in gdb.threads
Commit Message
Change gdb.threads to use clean_restart more consistently.
---
gdb/testsuite/gdb.threads/attach-stopped.exp | 9 +--------
gdb/testsuite/gdb.threads/fork-thread-pending.exp | 6 +-----
gdb/testsuite/gdb.threads/schedlock.exp | 6 +-----
gdb/testsuite/gdb.threads/watchthreads.exp | 6 +-----
4 files changed, 4 insertions(+), 23 deletions(-)
@@ -32,11 +32,8 @@ remote_exec build "rm -f ${binfile}"
#log_user 1
proc corefunc { threadtype } {
- global srcfile
global binfile
global escapedbinfile
- global srcdir
- global subdir
global gdb_prompt
set test_spawn_id [spawn_wait_for_attach $binfile]
@@ -45,11 +42,7 @@ proc corefunc { threadtype } {
# Stop the program
remote_exec build "kill -s STOP ${testpid}"
- # Start with clean gdb
- gdb_exit
- gdb_start
- gdb_reinitialize_dir $srcdir/$subdir
- gdb_load ${binfile}
+ clean_restart $binfile
# Verify that we can attach to the stopped process.
@@ -79,11 +79,7 @@ gdb_test_multiple "info threads" "$test" {
# Start over, but this time, don't switch away from the fork event thread.
-gdb_exit
-gdb_start
-gdb_reinitialize_dir $srcdir/$subdir
-
-gdb_load ${binfile}
+clean_restart $binfile
if {![runto_main]} {
return 0
}
@@ -146,11 +146,7 @@ proc step_ten_loops { cmd } {
}
}
-# Start with a fresh gdb.
-
-gdb_exit
-gdb_start
-gdb_reinitialize_dir $srcdir/$subdir
+clean_restart
# We'll need this when we send_gdb a ^C to GDB. Need to do it before we
# run the program and gdb starts saving and restoring tty states.
@@ -31,11 +31,7 @@ if {[gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executab
return -1
}
-gdb_exit
-gdb_start
-gdb_reinitialize_dir $srcdir/$subdir
-gdb_load ${binfile}
-
+clean_restart $binfile
gdb_test_no_output "set can-use-hw-watchpoints 1" ""
#