From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18580 invoked by alias); 27 Nov 2006 13:51:49 -0000 Received: (qmail 18572 invoked by uid 22791); 27 Nov 2006 13:51:48 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 27 Nov 2006 13:51:41 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1GogtX-0008RZ-JX for gdb@sourceware.org; Mon, 27 Nov 2006 08:51:39 -0500 Date: Mon, 27 Nov 2006 13:51:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: usability: exiting from GDB Message-ID: <20061127135138.GA32366@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <456A79B5.2020505@anu.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <456A79B5.2020505@anu.edu.au> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00175.txt.bz2 On Mon, Nov 27, 2006 at 04:37:57PM +1100, John Pye wrote: > What I would like is that (a) the 'ctrl-C' behaviour from the gdb prompt > was changed so that instead of (I think uselessly) outputting 'Quit' and > bringing up another prompt line, it actually *did* quit GDB. As Eli explained, that's not a good idea. You could accidentally quit GDB while trying to interrupt your program. Does C-c quit shells? No, it just kills the current input line. > Or, > alternatively, (b) that the following prompted could somehow be > persistently disabled: "The program is running. Exit anyway? (y or n)". > > I often find that in exiting GDB, which requires ctrl-D to be pressed > twice, I press ctrl-D three times and end up also logging out of my > terminal program, which is annoying. I don't know about you, but my shell prints a warning message if I try to C-d while there are background jobs running. GDB's behaving exactly the same :-) You can't disable just that one prompt, but you could disable prompts with "set confirm off". > Another issue is that after exiting GDB via ctrl-D-ctrl-D, GDB doesn't > output a newline, which causes the following bash input line to be > messed up. This has been reported as a bug before; it ought to be easy to fix. -- Daniel Jacobowitz CodeSourcery