From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5915 invoked by alias); 5 Nov 2009 08:10:32 -0000 Received: (qmail 5905 invoked by uid 22791); 5 Nov 2009 08:10:31 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx.southnet.co.nz (HELO viper.snap.net.nz) (202.37.101.20) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 05 Nov 2009 08:10:27 +0000 Received: from totara (12.25.255.123.static.snap.net.nz [123.255.25.12]) by viper.snap.net.nz (Postfix) with ESMTP id DEC903DABA4; Thu, 5 Nov 2009 21:10:24 +1300 (NZDT) Received: by totara (Postfix, from userid 1000) id D4F04C167; Thu, 5 Nov 2009 21:10:23 +1300 (NZDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19186.34927.781254.301460@totara.tehura.co.nz> Date: Thu, 05 Nov 2009 08:10:00 -0000 To: Marco Menegazzi Cc: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= , gdb@sourceware.org Subject: Re: GDB GUI In-Reply-To: <0F6AD058-C87F-4E6E-9CA2-0B7F2342AD5E@gmail.com> References: <100F84AB-4BCE-427F-9796-3D2162D97DC9@gmail.com> <200911021436.46359.sergiodj@linux.vnet.ibm.com> <0F6AD058-C87F-4E6E-9CA2-0B7F2342AD5E@gmail.com> From: nickrob@snap.net.nz (Nick Roberts) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00047.txt.bz2 > ... but then I ask myself why to use gdb/mi that > returns a more complex output instead of calling directly gdb and > parse the stout to get what I want? Because, over time, normal GDB output is likely to change in a way that will break your parser. In contrast, GDB/MI output shouldn't change in unexpected ways.