From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12912 invoked by alias); 11 Jul 2005 08:08:08 -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 12731 invoked by uid 22791); 11 Jul 2005 08:08:00 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 11 Jul 2005 08:08:00 +0000 Received: from farnswood.snap.net.nz (p187-tnt2.snap.net.nz [202.124.108.187]) by viper.snap.net.nz (Postfix) with ESMTP id E1E205DCA07; Mon, 11 Jul 2005 20:07:56 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 3485362A99; Mon, 11 Jul 2005 09:10:05 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17106.10589.435150.575928@farnswood.snap.net.nz> Date: Mon, 11 Jul 2005 08:08:00 -0000 To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: Formatting of function pointer value In-Reply-To: References: <20050708135810.GB17089@nevyn.them.org> <17106.5796.850869.491390@farnswood.snap.net.nz> X-SW-Source: 2005-07/txt/msg00103.txt.bz2 > > CLI output is intended for the user. It can change with a new release, > > and on the state of execution in ways which are not easy to anticipate > > without reading the source code. Provided that it still makes sense, > > that is not a problem to the user but it can be to a frontend, if it is > > trying to parse the output in a very precise manner. MI has a more > > formal syntax and so is not as variable. Once it is fully developed, > > So it's not stable yet? The manual says: Note that GDB/MI is still under construction, so some of the features described below are incomplete and subject to change. > > its output should be stable and if > > it does change, some backward compatibility will probably be maintained. > > Ok, the the only advantage of MI is stable output format. I've not said that. It also uses variable objects, it aims to be asynchronous... > Can you tell me how it's achieved? As I've already said, it has a more formal syntax. > For example, looking at the code that prints function values (what worries > me in the first place): > > fprintf_filtered (stream, "{"); > type_print (type, "", stream, -1); > fprintf_filtered (stream, "} "); I don't understand the point of the example. > As I right in assuming that exactly the same output will be produced for MI > mode and for CLI mode? No, you're wrong to assume that. That should be clear from the examples in the manual. Nick > If so, then how MI can be more stable than CLI, if the output is the same?