From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25343 invoked by alias); 11 Jul 2005 07:21:11 -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 25330 invoked by uid 22791); 11 Jul 2005 07:21:07 -0000 Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 11 Jul 2005 07:21:07 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1DrsaO-0006Wd-A7 for gdb@sources.redhat.com; Mon, 11 Jul 2005 09:20:16 +0200 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jul 2005 09:20:16 +0200 Received: from ghost by zigzag.lvk.cs.msu.su with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jul 2005 09:20:16 +0200 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: Formatting of function pointer value Date: Mon, 11 Jul 2005 07:21:00 -0000 Message-ID: References: <20050708135810.GB17089@nevyn.them.org> <17106.5796.850869.491390@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.8.2 X-SW-Source: 2005-07/txt/msg00101.txt.bz2 Nick Roberts wrote: > > > It is a feature, not a bug. Why is your frontend using the > > > command-line interface? > > > > Well, the debugger part in KDevelop was not written by me, so I don't > > know why command-line interface, and not MI is used. > > > > > DON'T do that! Use MI nowadays, please please > > > please. > > > > I'm sorry, but section 24 of gdb manual does not say why MI is better. > > Can you give the reasons? > > 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? > 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. Can you tell me how it's achieved? 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, "} "); As I right in assuming that exactly the same output will be produced for MI mode and for CLI mode? If so, then how MI can be more stable than CLI, if the output is the same? - Volodya