From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26928 invoked by alias); 12 Apr 2007 06:40:10 -0000 Received: (qmail 26918 invoked by uid 22791); 12 Apr 2007 06:40:09 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 12 Apr 2007 07:40:05 +0100 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HbsyK-0005UU-Bh for gdb-patches@sources.redhat.com; Thu, 12 Apr 2007 08:39:56 +0200 Received: from wind.lvk.cs.msu.su ([158.250.17.9]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Apr 2007 08:39:56 +0200 Received: from ghost by wind.lvk.cs.msu.su with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Apr 2007 08:39:56 +0200 To: gdb-patches@sources.redhat.com From: Vladimir Prus Subject: Re: [RFA] set debug mi Date: Thu, 12 Apr 2007 06:40:00 -0000 Message-ID: References: <1176335457.26620.48.camel@svmsnyderlnx.palmsource.com> <2FBCCFDF-95E9-43E5-88A3-F2B26EDC5CE0@apple.com> <1176339097.26620.55.camel@svmsnyderlnx.palmsource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.2 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00157.txt.bz2 Michael Snyder wrote: > On Wed, 2007-04-11 at 17:42 -0700, Jason Molenda wrote: >> On Apr 11, 2007, at 4:50 PM, Michael Snyder wrote: >> >> > Anybody think this is useful? >> >> We do something similar at Apple but we have our front-end program >> deal with it. The UI has a preference to save the mi log to a file; >> it saves all communication between gdb and the FE to that file. It's >> invaluable for debugging bug reports - it's invariably the first thing >> we ask for when someone reports a bug against our debugger. Besides >> pointing the finger at either gdb or the front-end it has the benefit >> of showing exactly what commands were sent to the debugger, instead of >> relying on the user's memory of the same. >> >> I think the approach of having all I/O between the debugger and the FE >> saved is superior but having something like this built in to gdb could >> be helpful for people who can't do that easily in the FE. > > Eclipse also has a similar option. I just thought it might be > handy to have the facility on the gdb end as well. By obvious > analogy with "debug remote". And KDevelop too. But I think this is better to be done in frontend. Frontend would probably want to have logs of all debugger interaction shown to the user, including CLI commands, so having a log file with just MI commands somewhere won't help. - Volodya