From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7822 invoked by alias); 19 May 2006 17:55:22 -0000 Received: (qmail 7808 invoked by uid 22791); 19 May 2006 17:55:22 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao05.cox.net (HELO eastrmmtao05.cox.net) (68.230.240.34) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 19 May 2006 17:55:19 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao05.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060519175517.LGVH26910.eastrmmtao05.cox.net@localhost.localdomain>; Fri, 19 May 2006 13:55:17 -0400 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1Fh9C6-0000TG-LX; Fri, 19 May 2006 13:55:22 -0400 Date: Fri, 19 May 2006 19:22:00 -0000 From: Bob Rossi To: Jim Blandy Cc: gdb@sources.redhat.com Subject: Re: invoking GDB from FE and signals Message-ID: <20060519175522.GA30002@brasko.net> Mail-Followup-To: Jim Blandy , gdb@sources.redhat.com References: <3518719F06577C4F85DA618E3C37AB91054A9EFD@nimbus.ott.qnx.com> <20060518172253.GE21003@brasko.net> <20060519005831.GG21003@brasko.net> <20060519025453.GA24453@nevyn.them.org> <20060519105945.GC31982@brasko.net> <20060519124919.GB750@nevyn.them.org> <20060519134221.GC26750@brasko.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i 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/msg00317.txt.bz2 On Fri, May 19, 2006 at 10:17:02AM -0700, Jim Blandy wrote: > > Bob Rossi writes: > > On Fri, May 19, 2006 at 08:49:19AM -0400, Daniel Jacobowitz wrote: > >> On Fri, May 19, 2006 at 06:59:45AM -0400, Bob Rossi wrote: > >> > OK, you could not be more correct. I want GDB to handle it, not the FE. > >> > However, how do I let "GDB handle it", while using the 'set tty' > >> > command? I guess that's the question I've been asking all along. > >> > >> Make it trap the SIGINT and do something sensible with it. > > > > OK, so, does anyone think this suggestion would have drawbacks? > > That is, modify GDB so that the FE can always send the signal to the GDB > > pty, and GDB will figure out what to do with the signal. This would be a > > wonderful solution. That way, if the FE is using 'set tty' or not, it > > could always send the signal to the same place. > > I totally think you should be using 'set tty'. It's the only way to > keep inferior and GDB output straight, and nobody has ever had the > forbearance to explain the drawbacks to me. > > I still think it's odd that you would actually want a way to send a > SIGINT to either the inferior if running or GDB otherwise. But if you > really do want that, then making GDB deal with it seems like the right > thing. Jim, the user can do this exact sort of thing just using plain old GDB. They don't even know they are doing it probably, they just hit ^c. So, it's not that I want to send ^c to GDB or inferior, I just want to do what the user wants. OK, I have to assume you know more about this than I do. You've been doing it for much longer. Where does your FE send the ^c when GDB is running? when inferior is running? Anyone maintaining an FE using the 'set tty', what does your FE do when it get's a ^c under these 2 case's? Thanks, Bob Rossi