Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
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 15:45:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0712071517490.31587@perivale.mips.com> (raw)
In-Reply-To: <20071207151058.GA6243@caradoc.them.org>

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


  reply	other threads:[~2007-12-07 15:36 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 [this message]
2007-12-07 16:21           ` Daniel Jacobowitz

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=Pine.LNX.4.61.0712071517490.31587@perivale.mips.com \
    --to=macro@mips.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.com \
    --cc=macro@linux-mips.org \
    /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