Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Jim Blandy <jimb@codesourcery.com>,
	gdb-patches@sourceware.org,
		"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Target-specific command logging facility
Date: Fri, 07 Dec 2007 16:21:00 -0000	[thread overview]
Message-ID: <20071207154538.GA10618@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0712071517490.31587@perivale.mips.com>

On Fri, Dec 07, 2007 at 03:36:05PM +0000, Maciej W. Rozycki wrote:
>  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.

Ah, I see.  Yes, that does sound useful.  Perhaps we should get MI
targets to log commands similarly, if they don't already, and a way to
do this same nice trick to stubs speaking the ordinary remote protocol.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-12-07 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 15:44 Maciej W. Rozycki
2007-11-29 18:20 ` Jim Blandy
2007-11-30 13:55   ` Maciej W. Rozycki
2007-12-07 15:07     ` Maciej W. Rozycki
2007-12-07 15:36       ` Daniel Jacobowitz
2007-12-07 15:45         ` Maciej W. Rozycki
2007-12-07 16:21           ` Daniel Jacobowitz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071207154538.GA10618@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox