From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18762 invoked by alias); 12 May 2003 18:57:09 -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 6331 invoked from network); 12 May 2003 18:43:32 -0000 Received: from unknown (HELO nick.uklinux.net) (194.247.49.99) by sources.redhat.com with SMTP; 12 May 2003 18:43:32 -0000 Received: by nick.uklinux.net (Postfix, from userid 501) id 0C21675FDD; Sun, 11 May 2003 21:13:20 +0100 (BST) From: Nick Roberts To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: GDB 6 In-Reply-To: <3EBE69AE.30001@redhat.com> References: <16061.32163.69181.411133@nick.uklinux.net> <3EBE69AE.30001@redhat.com> Message-Id: <20030511201320.0C21675FDD@nick.uklinux.net> Date: Mon, 12 May 2003 18:57:00 -0000 X-SW-Source: 2003-05/txt/msg00202.txt.bz2 > > 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 <-- Using break instead of tbreak, the breakpoint annotation is issued before frame-begin which tells Emacs that output is now from Gdb and not the inferior. Before frame-begin is deleted, can Gdb issue another annotation (stopping ?) prior to printing frame details so that Emacs will always understand that this is output from Gdb? Also Emacs doesn't need prompt-for-continue. Nick