Re: RFC: Don't kill the program after "file"

Fred Fish
2006-08-01T20:17:42Z

I'm currently getting new failures with a mips-elf toolchain, and
other toolchains, when using the simulator for testing. I'm not
entirely sure that they are due to this change, but it seems likely.

Here is a snippet from the gdb.log file:

(gdb) dir /src/latest/trunk/src/gdb/gdb/testsuite/gdb.base
Source directories searched: /src/latest/trunk/src/gdb/gdb/testsuite/gdb.base:$cdir:$cwd
(gdb) kill
The program is not being run.
(gdb) file /links/build/latest/trunk/mips-elf/gdb/gdb/testsuite/gdb.base/opaque
A program is being debugged already.
Are you sure you want to change the file? (y or n) ERROR: couldn't load /links/build/latest/trunk/mips-elf/gdb/gdb/testsuite/gdb.base/opaque into /links/build/latest/trunk/mips-elf/gdb/gdb/testsuite/../../gdb/gdb (timed out).
delete breakpoints
Please answer y or n.
A program is being debugged already.
Are you sure you want to change the file? (y or n) ERROR: Delete all breakpoints in delete_breakpoints (timeout)
break main
Please answer y or n.
A program is being debugged already.
Are you sure you want to change the file? (y or n) UNRESOLVED: gdb.base/opaque.exp: setting breakpoint at main (timeout)
ERROR: cannot run to breakpoint at main
ERROR: Got interactive prompt.
UNRESOLVED: gdb.base/opaque.exp: whatis on opaque struct pointer (dynamically)
ERROR: Got interactive prompt.
UNRESOLVED: gdb.base/opaque.exp: ptype on opaque struct pointer (dynamically) 1
ERROR: Got interactive prompt.