From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4330 invoked by alias); 7 Dec 2007 15:36:24 -0000 Received: (qmail 4310 invoked by uid 22791); 7 Dec 2007 15:36:23 -0000 X-Spam-Check-By: sourceware.org Received: from dmz.mips-uk.com (HELO dmz.mips-uk.com) (194.74.144.194) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 07 Dec 2007 15:36:19 +0000 Received: from internal-mx1 ([192.168.192.240] helo=ukservices1.mips.com) by dmz.mips-uk.com with esmtp (Exim 3.35 #1 (Debian)) id 1J0fFO-00070k-00; Fri, 07 Dec 2007 15:36:14 +0000 Received: from perivale.mips.com ([192.168.192.200]) by ukservices1.mips.com with esmtp (Exim 3.36 #1 (Debian)) id 1J0fFF-0007xI-00; Fri, 07 Dec 2007 15:36:05 +0000 Received: from macro (helo=localhost) by perivale.mips.com with local-esmtp (Exim 4.63) (envelope-from ) id 1J0fFF-0000RK-Qu; Fri, 07 Dec 2007 15:36:05 +0000 Date: Fri, 07 Dec 2007 15:45:00 -0000 From: "Maciej W. Rozycki" To: Daniel Jacobowitz cc: Jim Blandy , gdb-patches@sourceware.org, "Maciej W. Rozycki" Subject: Re: Target-specific command logging facility In-Reply-To: <20071207151058.GA6243@caradoc.them.org> Message-ID: References: <20071207151058.GA6243@caradoc.them.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MIPS-Technologies-UK-MailScanner: Found to be clean X-MIPS-Technologies-UK-MailScanner-From: macro@mips.com 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-12/txt/msg00129.txt.bz2 On Fri, 7 Dec 2007, Daniel Jacobowitz wrote: > > Having seen no objections I have committed it now. > > Jim approved this, so it's fine - but could you explain the use case > for this? Why should it be target specific? MDI support provides its own logging facility which lets the user ask for commands issued to GDB to be passed down to the target. The target may than place these commands within its own log file (which will typically provide additional data beyond the scope of GDB itself, such as the record of transactions performed at the JTAG port) which lets one see what actions at the target result from each of the GDB command. Useful for debugging the MDI target itself. Being self-contained I resisted from submitting this change together with MDI not to obfuscate the view. I should be able to submit the MDI change pretty soon now, though I have to take your suggestion on the handling of threads first. Maciej