From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24922 invoked by alias); 15 May 2006 18:12:02 -0000 Received: (qmail 24914 invoked by uid 22791); 15 May 2006 18:12:02 -0000 X-Spam-Check-By: sourceware.org Received: from e34.co.us.ibm.com (HELO e34.co.us.ibm.com) (32.97.110.152) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 15 May 2006 18:11:58 +0000 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e34.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4FIBtuc030177 for ; Mon, 15 May 2006 14:11:55 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4FIBtrI174632 for ; Mon, 15 May 2006 12:11:55 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k4FIBsLA001578 for ; Mon, 15 May 2006 12:11:54 -0600 Received: from dufur.beaverton.ibm.com (dufur.beaverton.ibm.com [9.47.22.20]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k4FIBn0r000999; Mon, 15 May 2006 12:11:49 -0600 Subject: Re: invoking GDB from FE and signals From: PAUL GILLIAM Reply-To: pgilliam@us.ibm.com To: Daniel Jacobowitz Cc: gdb@sourceware.org In-Reply-To: <20060513154816.GA5022@nevyn.them.org> References: <20060513141920.GC10678@brasko.net> <20060513145421.GA3664@nevyn.them.org> <20060513151026.GD10678@brasko.net> <20060513151057.GA4112@nevyn.them.org> <20060513152021.GE10678@brasko.net> <20060513154816.GA5022@nevyn.them.org> Content-Type: text/plain Date: Mon, 15 May 2006 18:42:00 -0000 Message-Id: <1147712871.3672.153.camel@dufur.beaverton.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 (2.2.2-5) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00210.txt.bz2 On Sat, 2006-05-13 at 11:48 -0400, Daniel Jacobowitz wrote: > On Sat, May 13, 2006 at 11:20:21AM -0400, Bob Rossi wrote: > > When I say "the supported way", I'm assuming there is a way GDB provides > > for FE's to work with it in regards to sending signals, in particularly > > ^c. > > But there isn't :-) > > > If GDB doesn't provide this functionality and it's mere hackers > > chance that all of us FE's are getting this to work most of the time, > > then I understand what you mean. > > > > Othewise, if GDB has been designed to accept signal during certain > > circumstances, and not during others, I would love to know what those > > are so that I can benefit from using this functionality. > > If there were such a design, hopefully, it would be in the manual. All > of this is generally legacy from the GDB CLI, which is designed to work > with the host's job control. When the inferior is running and you > press Control-C, the signal goes to the inferior, not to GDB. > > Your needs may be different. Just to add a little detail about the 'normal' case: You press , the tty handler intercepts it and sends a signal to the inferior. Because the inferior is being debugged, *any* signal causes it to stop, letting the debugger know that it stopped due to a particular signal. When gdb causes the inferior to run again, gdb decides if the signal should be 'passed through' to the inferior'. I hope I'm not being pedantic. -=# Paul #=-