From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: gdb with many windows: kill associated buffers doesn't always work Date: Tue, 23 May 2006 21:29:50 +1200 Message-ID: <17522.54798.555541.900063@kahikatea.snap.net.nz> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1148376654 16983 80.91.229.2 (23 May 2006 09:30:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 23 May 2006 09:30:54 +0000 (UTC) Cc: schwab@suse.de, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 23 11:30:47 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FiTDq-0003O2-4U for ged-emacs-devel@m.gmane.org; Tue, 23 May 2006 11:30:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FiTDp-00027E-2a for ged-emacs-devel@m.gmane.org; Tue, 23 May 2006 05:30:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FiTDd-00026B-4C for emacs-devel@gnu.org; Tue, 23 May 2006 05:30:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FiTDZ-00024C-2g for emacs-devel@gnu.org; Tue, 23 May 2006 05:30:24 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FiTDY-000249-VO for emacs-devel@gnu.org; Tue, 23 May 2006 05:30:21 -0400 Original-Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FiTHk-0001w5-5Y for emacs-devel@gnu.org; Tue, 23 May 2006 05:34:40 -0400 Original-Received: from kahikatea.snap.net.nz (p367-tnt1.snap.net.nz [202.124.111.113]) by viper.snap.net.nz (Postfix) with ESMTP id 9EF71756E00; Tue, 23 May 2006 21:30:19 +1200 (NZST) Original-Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id 4604A1D3550; Tue, 23 May 2006 21:29:52 +1200 (NZST) Original-To: Klaus Zeitler In-Reply-To: X-Mailer: VM 7.19 under Emacs 22.0.50.13 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:55113 Archived-At: Klaus Zeitler writes: > 1. emacs -Q& > 2. eval (setq gdb-many-windows t) > 3. M-x gdb > > Now when I finish my debug session, the associated buffers don't get killed > automatically. > When I restart gdb without killing those associated buffers, I see the same > behavior. But when I kill all associated buffers and then restart gdb, the > newly created associated buffers will be automatically killed when I finish > my gdb session. I assume that by "when I finish my debug session" you mean something like typing quit in the GUD buffer, so that the process is killed but not the GUD buffer. I'm not sure why you would want to type quit and not just kill the GUD buffer to finish a debug session, but clearly its a legitimate thing to do. This problem can be avoided by reverting this change: 2006-03-26 Andreas Schwab * progmodes/gud.el (gdb): Only complain about multiple debugging when the gdb process is still running. which wouldn't allow more than one GUD session (live process or not) with "-annotate=3". Andreas, What are the benefits of this change? I can see that you can keep the shell history in a second GUD buffer but that seems of limited usefulness. I can see many problems if the user is allowed to start a new session without the buffers of the first being killed first. -- Nick http://www.inet.net.nz/~nickrob