daemon@tut.cis.ohio-state.edu (Admin) (04/11/89)
The first time you hit ^C in gdb, it prints "Quit" and stops
what it's doing. The second time, it exits. This would be fine
if it only did this if the ^C's were typed one after the other,
but it also happens if I use a ^C to abort some long output
("Nooo. I don't want to see that many variables") and then use
one again at some later time (after many other commands have been
typed). It would be nice if typing a command reset the second ^C to just
interrupt the current op again.
There's a bunch of stuff in there now with "quit_flag" and "immediate_quit",
but I'll be jiggered if I understand it.
Jordanchrisb@mipon2.intel.com (Chris Benenati) (04/13/89)
In article <8904111610.AA02582@meepmeep.UUCP> daemon@tut.cis.ohio-state.edu (Admin) writes: > The first time you hit ^C in gdb, it prints "Quit" and stops > what it's doing. The second time, it exits. I'll bet you're running under System V Unix. Under System V, a signal reverts to its default handling unless the handler resets the signal. gdb fails to do this. I believe this is a gdb bug, not a feature, since under BSD it works as you'd expect.