Lines Matching full:quit
652 has finished executing. We can end our GDB session with the GDB `quit'
655 (gdb) quit
667 * type `quit' or `Ctrl-d' to exit.
672 * Quitting GDB:: How to quit GDB
886 * The user quits with an explicit value. E.g., `quit 1'.
1081 `quit [EXPRESSION]'
1083 To exit GDB, use the `quit' command (abbreviated `q'), or type an
2105 To quit debugging one of the running inferiors that is not the
2489 To quit debugging one of the forked processes, you can either detach
9016 disconnected from the target. Note that `detach' or `quit' will
25587 Approximately corresponds to `quit'.
26070 quit
26075 Here `quit' is input to GDB; the rest is output from GDB. The three
26158 Quit and error annotations indicate that any annotations which GDB
26166 A quit or error annotation may be preceded by
26170 Any output between that and the quit or error annotation is the error
28625 either quit GDB or create a core file of the current GDB session.
28636 Quit this debugging session? (y or n) n
28645 the user the opportunity to both quit GDB and create a core file
28650 `quit'
28652 quit. The default is to ask the user what to do.
30589 `quit' command.
37366 * q (quit): Quitting GDB. (line 6)
37413 * quit [EXPRESSION]: Quitting GDB. (line 6)
37414 * quit annotation: Errors. (line 6)
