From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21721 invoked by alias); 12 Apr 2007 00:42:53 -0000 Received: (qmail 21709 invoked by uid 22791); 12 Apr 2007 00:42:52 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 12 Apr 2007 01:42:50 +0100 Received: from relay7.apple.com (a17-128-113-37.apple.com [17.128.113.37]) by mail-out4.apple.com (8.13.8/8.13.8) with ESMTP id l3C0gmje021795; Wed, 11 Apr 2007 17:42:49 -0700 (PDT) Received: from relay7.apple.com (unknown [127.0.0.1]) by relay7.apple.com (Symantec Mail Security) with ESMTP id DFF8A304FB; Wed, 11 Apr 2007 17:42:48 -0700 (PDT) X-AuditID: 11807125-af663bb00000538d-98-461d8088cb4f Received: from [17.201.22.22] (moleja2.apple.com [17.201.22.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay7.apple.com (Apple SCV relay) with ESMTP id CA6C63043A; Wed, 11 Apr 2007 17:42:48 -0700 (PDT) Cc: gdb-patches@sources.redhat.com Message-Id: <2FBCCFDF-95E9-43E5-88A3-F2B26EDC5CE0@apple.com> From: Jason Molenda To: Michael Snyder In-Reply-To: <1176335457.26620.48.camel@svmsnyderlnx.palmsource.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v878) Subject: Re: [RFA] set debug mi Date: Thu, 12 Apr 2007 00:42:00 -0000 References: <1176335457.26620.48.camel@svmsnyderlnx.palmsource.com> X-Mailer: Apple Mail (2.878) 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/msg00153.txt.bz2 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. J