From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26932 invoked by alias); 11 May 2003 22:00:01 -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 26502 invoked from network); 11 May 2003 21:59:57 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 11 May 2003 21:59:57 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id A718A2B2F; Sun, 11 May 2003 17:59:56 -0400 (EDT) Message-ID: <3EBEC7DC.10609@redhat.com> Date: Sun, 11 May 2003 22:00:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Roberts Cc: gdb@sources.redhat.com Subject: Re: GDB 6 References: <16061.32163.69181.411133@nick.uklinux.net> <3EBE69AE.30001@redhat.com> <20030511201320.0C21675FDD@nick.uklinux.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00199.txt.bz2 > 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 <-- The testsuite now looks like: (gdb) ^Z^Zprompt PASS: gdb.base/annota3.exp: breakpoint info run ^Z^Zpost-prompt Starting program: /home/scratch/PENDING/2003-03-11-ann-3/N-powerpc-unknown-netbs d1.6/gdb/testsuite/gdb.base/annota3 ^Z^Zframes-invalid ^Z^Zframes-invalid ^Z^Zbreakpoints-invalid ^Z^Zstarting ^Z^Zframes-invalid ^Z^Zframes-invalid ^Z^Zframes-invalid ^Z^Zframes-invalid ^Z^Zbreakpoint 1 Breakpoint 1, main () at /home/scratch/PENDING/2003-03-11-ann-3/src/gdb/testsuit e/gdb.base/annota3.c:32 ^Z^Zsource /home/scratch/PENDING/2003-03-11-ann-3/src/gdb/testsuite/gdb.base/ann ota3.c:32:323:beg:0x1800bc8 ^Z^Zstopped ^Z^Zpre-prompt (gdb) Does this help? You get ^Z^Zbreakpoint 1 when the target hits that breakpoint. > 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. There are other places that could gain events if needed. > 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. Ok. Andrew