SIGINT handling in gdb

Thread View: gnu.gdb.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Admin Tue, 11 Apr 1989 14:21

#750

Author: Admin
Date: Tue, 11 Apr 1989 14:21

13 lines
1007 bytes

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.

						Jordan

Re: SIGINT handling in gdb

#751

Author: Chris Benenati
Date: Wed, 12 Apr 1989 21:15

11 lines
949 bytes

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.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads