From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: gdbui hang Date: 10 May 2004 08:22:58 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084178248 13528 80.91.224.253 (10 May 2004 08:37:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 10 May 2004 08:37:28 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon May 10 10:37:18 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BN6Hl-0000Hx-00 for ; Mon, 10 May 2004 10:37:17 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BN6Hl-0002TU-00 for ; Mon, 10 May 2004 10:37:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.33) id 1BN6H0-0005jH-KJ for emacs-devel@quimby.gnus.org; Mon, 10 May 2004 04:36:30 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.33) id 1BN6EG-0004Op-TD for emacs-devel@gnu.org; Mon, 10 May 2004 04:33:41 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.33) id 1BN66s-0001jg-7p for emacs-devel@gnu.org; Mon, 10 May 2004 04:26:35 -0400 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.33) id 1BN64Y-0001KL-1n for emacs-devel@gnu.org; Mon, 10 May 2004 04:23:38 -0400 Original-Received: (qmail 5413 invoked from network); 10 May 2004 08:23:36 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 10 May 2004 08:23:36 -0000 Original-To: emacs-devel@gnu.org In-Reply-To: Original-Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23026 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23026 Miles Bader writes: > Sometimes (well, actually fairly often) the new fancy gdb mode hangs in > a way that can't be interrupted, e.g.: > > ... > Program exited normally. > (gdb) break poc_startup > Function "poc_startup" not defined. > Make breakpoint pending on future shared library load? (y or [n]) n > > C-c C-c C-c C-c C-c C-c C-c C-c C-c C-c C-c C-c C-c C-c > > I'm not sure what other info is useful to debug this. I have seen similar problems if I set a breakpoints at some location (using C-x SPC) while the program is running; then I go to the gud buffer and type C-c C-z to stop the process. This seems to work, but sometimes it's like gud and gdb are no longer in sync. If I try to delete the breakpoint (e.g. d 4) it gets worse. If I then continue the program, c, I can no longer interrupt it with C-c C-z. Maybe you need to set two breakpoints at the same location (do C-x SPC twice) to see this. Sorry that I cannot be more precise. > > [A related problem is that if I kill the *gud-foo* buffer to try and > recover from the hang, and then start another gdb process, it will often > fail to work, saying `selecting deleted buffer' in a command I give. In > general it's a good idea to recover gracefully if a buffer is deleted; > the gdb mode probably shouldn't be keeping any session state outside of > the gdb buffer itself -- i.e., try to make any state variables > buffer-local in the gdb session buffer.] I've seen this too -- to me it looks like there is a process filter still running somewhere which tries to use a deleted buffer... -- Kim F. Storm http://www.cua.dk