Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bbn!apple!vsi1!wyse!td2cad!mipos3!omepd!mipon2!chrisb
From: chrisb@mipon2.intel.com (Chris Benenati)
Newsgroups: gnu.gdb.bug
Subject: Re: SIGINT handling in gdb
Message-ID: <4297@omepd.UUCP>
Date: 12 Apr 89 21:15:20 GMT
References: <8904111610.AA02582@meepmeep.UUCP>
Sender: news@omepd.UUCP
Reply-To: chrisb@mipon2.UUCP (Chris Benenati)
Distribution: gnu
Organization: Intel Corp., Hillsboro
Lines: 11

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.