* gdb.base/a1-selftest.exp: Don't test "maint dump-me". That test

was a vestige of the manual TESTSTRATEGY, and the purpose of it
	was to make sure that gdb can read a core file.  But (a) the "read
	the corefile" part didn't make it to a1-selftest.exp, we just
	delete the corefile after creating it, and (b) we test reading
	corefiles in corefile.exp anyway.  Also, this test left around a
	xgdb process on Solaris.

	* gdb.base/corefile.exp: Also test backtrace.
This commit is contained in:
Jim Kingdon 1995-01-11 20:42:33 +00:00
parent 788d94361f
commit 4a2170f0ea
2 changed files with 14 additions and 35 deletions

View File

@ -1,3 +1,15 @@
Wed Jan 11 14:37:04 1995 Jim Kingdon <kingdon@lioth.cygnus.com>
* gdb.base/a1-selftest.exp: Don't test "maint dump-me". That test
was a vestige of the manual TESTSTRATEGY, and the purpose of it
was to make sure that gdb can read a core file. But (a) the "read
the corefile" part didn't make it to a1-selftest.exp, we just
delete the corefile after creating it, and (b) we test reading
corefiles in corefile.exp anyway. Also, this test left around a
xgdb process on Solaris.
* gdb.base/corefile.exp: Also test backtrace.
Wed Jan 11 00:14:40 1995 Jeff Law (law@snake.cs.utah.edu)
* gdb.base/commands.exp: Test a simple user defined command with

View File

@ -449,41 +449,8 @@ GDB.*Copyright \[0-9\]+ Free Software Foundation, Inc..*$prompt $"\
fail "$description (timeout)"
}
}
# force GDB to dump core. On Solaris expect seems to not see the
# final message, even if gdb did dump core, so we check for the
# core dump explicitly if we time out.
#
# Some systems append "core" to the name of the program; others
# append the name of the program to "core".
system rm -f core core.gdb gdb.core
send "maint dump-me\n"
expect {
-re "maint dump-me.*Should GDB dump core.*y or n. $" {
send "y\n"
expect {
-re "Quit.*core dumped.*" { pass "GDB dumped core" }
-re "Program received signal SIGQUIT.*$prompt $" {
pass "GDB dumped core"
# This means we just told xgdb, not gdb, to dump core.
# Get out of gdb so that removing xgdb doesn't get
# test busy errors.
gdb_exit
}
-re "$prompt $" { fail "GDB dumped core" }
default {
if {[file exists core] || [file exists core.gdb] || [file exists gdb.core]} then {
pass "GDB dumped core"
} else {
fail "GDB dumped core"
}
}
}
}
-re ".*$prompt $" { fail "GDB dumped core" }
timeout { fail "(timeout) GDB dumped core" }
}
system rm -f core core.gdb gdb.core
gdb_exit
# Set the timeout back to the value it had when we were called.
set timeout $oldtimeout