Lines Matching full:exits
873 * GDB exits abnormally. E.g., due to an incorrect argument or
1995 retained after a process exits. Inferiors have unique identifiers that
3399 a signal that GDB is listening for, or exits. This is the case
3923 until it exits the loop. In contrast, a `next' command at the end
4670 When the inferior process exits, or GDB detaches from it, process
13075 debugs the specified program only once. When the program exits, or you
13076 detach from it, GDB closes the connection and `gdbserver' exits.
13079 multi-process mode. When the debugged program exits, or you detach
13187 `gdbserver' prints an error message and exits.
13790 These commands enable and disable tracing of entries into and exits
15673 exits. You can access this list through history expansion or
16476 This command exits the `while' loop in whose body it is included.
19142 exits and should only forcibly kill GDB if it fails to exit in
20327 executes until either a breakpoint is encountered or the program exits.
