From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20199 invoked by alias); 10 Jul 2002 21:40:58 -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 20139 invoked from network); 10 Jul 2002 21:40:56 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 10 Jul 2002 21:40:56 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 94FF53D22; Wed, 10 Jul 2002 17:40:52 -0400 (EDT) Message-ID: <3D2CA9E4.8030209@ges.redhat.com> Date: Wed, 10 Jul 2002 14:40:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020708 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg Watson Cc: gdb@sources.redhat.com Subject: Re: gdb/mi References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg00105.txt.bz2 > I have some questions/comments about gdb/mi if someone could help out: > > 1. I've configure gdb 5.2 with --enable-gdbmi and --with-uiout. However when I run "gdb --interpreter=mi" the initial messages are not in console stream output format, but later messages are. Is this by design? You mean the (C) startup message? No one has thought about that. (BTW, you no longer need to explicitly configure in GDB/MI, since 5.2, it has been enabled by default). > 2. When I run a target program, it's output is not in target stream output format. Should this be the case? It depends. This is a problem that has been discussed before on this list. If the target program is native then GDB would need to do something like play with pty's or start a separate terminal program. If the target is remote then the output being encapsulated depends on support for this in the remote protocol. > 3. The gdb/mi output syntax in the manual does not quite reflect reality. In particular the 'console-stream-output', 'target-stream-output' and 'log-stream-output' rules should be suffixed with 'nl'. Also, I've observed an 'out-of-band-record' appearing after a 'result-record' but the syntax doesn't allow this. I guess it should be something like: > > output -> (out-of-band-record)* [result-record] (out-of-band-record)* "(gdb)" nl Yes (but I'll fix it a different way). Good catch. Andrew