* gdb.arch/i386-unwind.exp: Use gdb_run_cmd and gdb_expect instead

of gdb_test "run".
This commit is contained in:
Mark Kettenis 2003-11-23 21:14:45 +00:00
parent cb137aa501
commit 7027acc712
2 changed files with 20 additions and 2 deletions

View file

@ -1,3 +1,8 @@
2003-11-23 Mark Kettenis <kettenis@gnu.org>
* gdb.arch/i386-unwind.exp: Use gdb_run_cmd and gdb_expect instead
of gdb_test "run".
2003-11-23 Mark Kettenis <kettenis@gnu.org>
* gdb.arch/i386-unwind.exp: Don't use runto_main. Change

View file

@ -47,8 +47,21 @@ gdb_load ${binfile}
# Testcase for backtrace/1435.
gdb_test "run" "Program received signal SIGTRAP.*" \
"run past gdb1435"
# We use gdb_run_cmd so this stands a chance to work for remote
# targets too.
gdb_run_cmd
gdb_expect {
-re "Program received signal SIGTRAP.*$gdb_prompt $" {
pass "run past gdb1435"
}
-re ".*$gdb_prompt $" {
fail "run past gdb1435"
}
timeout {
fail "run past gdb1435 (timeout)"
}
}
gdb_test "backtrace 10" \
"#1\[ \t]*$hex in gdb1435.*\r\n#2\[ \t\]*$hex in main.*" \