Next: Debugging Multiple Inferiors Connections and Programs, Previous: Debugging an Already-running Process, Up: Running Programs Under ROCGDB [Contents][Index]
killKill the child process in which your program is running under ROCGDB.
This command is useful if you wish to debug a core dump instead of a running process. ROCGDB ignores any core dump file while your program is running.
On some operating systems, a program cannot be executed outside ROCGDB
while you have breakpoints set on it inside ROCGDB. You can use the
kill command in this situation to permit running your program
outside the debugger.
The kill command is also useful if you wish to recompile and
relink your program, since on many systems it is impossible to modify an
executable file while it is running in a process. In this case, when you
next type run, ROCGDB notices that the file has changed, and
reads the symbol table again (while trying to preserve your current
breakpoint settings).