Lines Matching refs:Quit

40175            Quit this debugging session? (y or n)
42957               0 Quit
46213           Quit^[[K^M^[[B(gdb) PASS: gdb.tui/pr30056.exp: Control-C
60289           Quit this debugging session? (y or n)
63553           Quit
63568           - in response to the "q\n" we get "Quit\n(gdb) "
63584           Quit
69156             Quit
69239           friends, a Ctrl-C _also_ results in a Quit exception, from the same
69264           and we should see 10 "Quit" being printed on the screen.  As if the
69269             (gdb) Quit   <<< Ctrl-C
69270             (gdb) Quit   <<< Ctrl-C
69277             (gdb) Quit
69280           Just one Quit, and nothing else.  If we look at the thread's state, we see:
69292             (gdb) Quit
69317            (gdb) Quit
69318            (gdb) Quit
69319            (gdb) Quit
69320            (gdb) Quit
69321            (gdb) Quit
69322            (gdb) Quit
69323            (gdb) Quit
69324            (gdb) Quit
69325            (gdb) Quit
69326            (gdb) Quit
71724           while the Quit portion is printed by the bottom GDB.  As the
71730           second one expect "Quit"  and the "(xgdb)" prompt from
72872           (gdb) Quit^M
92379           Quit anyway? (y or n) y
92411           Quit anyway? (y or n) y
92449           Quit anyway? (y or n) y
103467           - expect times out waiting for "Quit", the expected reaction for ^C
114424               Quit this debugging session? (y or n)
132002 …Quit this debugging session? (y or n) ../../src.dev-1/gdb/ser-event.c:212:16: runtime error: membe…
132039           see the same "Quit this debugging session? (y or n)" prompt, but when
139293               | Quit this debugging session? (y or n) y
140910           Quit this debugging session? (y or n) Recursive internal problem.
140917                         -re "Quit this debugging session\\? \\(y or n\\) $" {
140940           Quit this debugging session? (y or n) Recursive internal problem.
164779           Quit anyway? (y or n) monitor exit^M
164785           Quit anyway? (y or n) WARNING: Timed out waiting for EOF in server after monitor exit
167312            Quit
167318           Ctrl-C.  But somehow, that resulted in GDB printing "Quit", instead of
167335                 Quit.
167796             Quit this debugging session? (y or n) y
170373           (gdb) Quit^M
171834           Quit this debugging session? (y or n)
171869                       -re "Quit this debugging session\\? \\(y or n\\) $" {
176843               Quit this debugging session? (y or n) n
179290 …Quit this debugging session? (y or n) FAIL: gdb.btrace/enable-new-thread.exp: continue to breakpoi…
182376               Quit this debugging session? (y or n)