From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: gud breakage: ^done,changelist=[] Date: Wed, 27 Oct 2004 21:43:17 +1300 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: <16767.24485.426051.737854@farnswood.snap.net.nz> References: <87zn2ktlim.fsf@peder.flower> <16755.42540.548120.883521@farnswood.snap.net.nz> <87acukte3e.fsf@peder.flower> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1098867016 14899 80.91.229.6 (27 Oct 2004 08:50:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 27 Oct 2004 08:50:16 +0000 (UTC) Cc: emacs-devel@gnu.org, Jan Nieuwenhuizen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 27 10:50:04 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CMjVM-0000A6-00 for ; Wed, 27 Oct 2004 10:50:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CMjd5-0000ap-9Q for ged-emacs-devel@m.gmane.org; Wed, 27 Oct 2004 04:58:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CMjci-0000ai-LR for emacs-devel@gnu.org; Wed, 27 Oct 2004 04:57:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CMjci-0000aW-5A for emacs-devel@gnu.org; Wed, 27 Oct 2004 04:57:40 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CMjch-0000aT-Sc for emacs-devel@gnu.org; Wed, 27 Oct 2004 04:57:40 -0400 Original-Received: from [202.124.110.57] (helo=farnswood.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CMjUW-0004Ps-8s; Wed, 27 Oct 2004 04:49:13 -0400 Original-Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 61A3D627EE; Wed, 27 Oct 2004 09:43:18 +0100 (BST) Original-To: storm@cua.dk (Kim F. Storm) In-Reply-To: X-Mailer: VM 6.97 under Emacs 21.2.1 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:29027 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:29027 > I also see the flood of frames-invalid from time to time when > debugging emacs -- I reported that a long time ago. > Having looked at Jan's log, I think I know what is happening now. I think the problem occurs when the user enters the next gdb command before the previous one has finished. This real-time aspect to the problem would explain why the bug might be hard to reproduce. Jan, can you tell me if the bug is still there, even if you step through lilypond slowly. So, in the short term, with care (albeit tedious), this problem should be avoidable. In the longer term, I'll try to sort it. Nick FWIW, the offending code is: (defun gdb-send (proc string) "A comint send filter for gdb. This filter may simply queue output for a later time." (if gud-running (process-send-string proc (concat string "\n") (gdb-enqueue-input (concat string "\n"))) If gud-running is non-nil, the input jumps the code. This was meant to allow input to the inferior, but will also occur if the user has fast fingers e.g presses before the previous step has finished.