From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3709 invoked by alias); 6 Nov 2009 10:56:07 -0000 Received: (qmail 3700 invoked by uid 22791); 6 Nov 2009 10:56:07 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-bw0-f219.google.com (HELO mail-bw0-f219.google.com) (209.85.218.219) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 06 Nov 2009 10:56:03 +0000 Received: by bwz19 with SMTP id 19so1108923bwz.8 for ; Fri, 06 Nov 2009 02:56:01 -0800 (PST) Received: by 10.204.3.219 with SMTP id 27mr4442356bko.127.1257504961018; Fri, 06 Nov 2009 02:56:01 -0800 (PST) Received: from ?11.243.122.239? (93-39-87-161.ip75.fastwebnet.it [93.39.87.161]) by mx.google.com with ESMTPS id 15sm962510bwz.12.2009.11.06.02.55.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 06 Nov 2009 02:55:59 -0800 (PST) Subject: Re: GDB GUI Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Marco Menegazzi In-Reply-To: <19186.34927.781254.301460@totara.tehura.co.nz> Date: Fri, 06 Nov 2009 16:41:00 -0000 Cc: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= , gdb@sourceware.org Content-Transfer-Encoding: 7bit Message-Id: <3FD374F3-B19F-4764-B85D-4A8CC85816F1@gmail.com> References: <100F84AB-4BCE-427F-9796-3D2162D97DC9@gmail.com> <200911021436.46359.sergiodj@linux.vnet.ibm.com> <0F6AD058-C87F-4E6E-9CA2-0B7F2342AD5E@gmail.com> <19186.34927.781254.301460@totara.tehura.co.nz> To: Nick Roberts 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/msg00064.txt.bz2 So if I am not interested in future developements of gdb, because I am not working on a gdb frontend but I only need to use gdb under my graphical application, could it be useful to interact with gdb instead of gdb/mi ? It is just a question to understand if I really need to use gdb-mi in my case ... Thank you all for the answers. Il giorno 05/nov/2009, alle ore 09.10, Nick Roberts ha scritto: >> ... 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.