From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9578 invoked by alias); 12 May 2003 19:36:57 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9458 invoked from network); 12 May 2003 19:36:56 -0000 Received: from unknown (HELO white) (68.14.146.65) by sources.redhat.com with SMTP; 12 May 2003 19:36:56 -0000 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 19FJ6T-0004px-00; Mon, 12 May 2003 15:36:53 -0400 Date: Mon, 12 May 2003 19:36:00 -0000 From: Bob Rossi To: Nick Roberts Cc: Andrew Cagney , gdb@sources.redhat.com Subject: Re: GDB 6 Message-ID: <20030512193653.GB18114@white> Mail-Followup-To: Nick Roberts , Andrew Cagney , gdb@sources.redhat.com References: <16061.32163.69181.411133@nick.uklinux.net> <3EBE69AE.30001@redhat.com> <20030511201320.0C21675FDD@nick.uklinux.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030511201320.0C21675FDD@nick.uklinux.net> User-Agent: Mutt/1.3.28i X-SW-Source: 2003-05/txt/msg00206.txt.bz2 On Sun, May 11, 2003 at 09:13:20PM +0100, Nick Roberts wrote: > > > > Here is a revised and reduced list of annotations that I think I could > > > work with: > > > > > > frames-invalid > > > breakpoints-invalid > > > pre-prompt > > > prompt > > > commands > > > overload-choice > > > query > > > prompt-for-continue > > > post-prompt > > > source > > > starting > > > exited > > > signalled > > > signal > > > breakpoint > > > watchpoint > > > frame-begin > > > stopped > > > > I'm not sure about frame begin. Things like frames-invalid are events > > and they can stay (forever? ...). > > > > I don't really need frame-begin. The problem that I have, however, is that > frame-begin (and other annotations) are issued *before* stopped. This meant > that sometimes Emacs thought that frame details output by Gdb were output by > the inferior and so they were displayed in the IO buffer. I can only reproduce > this problem now with tbreak where a typical annotation sequence (avoiding > many repeats) looks like: > > frames-invalid > breakpoints-invalid > starting <-- > frames-invalid > breakpoints-invalid > frame-begin etc <-- > source > frame-end > stopped <-- > Also, do you relize that breakpoint-invalid is buggy? For many versions, gdb will not output breakpoints-invalid when you delete the last breakpoint in the list. so, b main delete main you will not get a breakpoints-invalid and emacs will still be displaying a breakpoint. Bob Rossi