This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Target-specific command logging facility
- From: "Maciej W. Rozycki" <macro at mips dot com>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: Jim Blandy <jimb at codesourcery dot com>, gdb-patches at sourceware dot org, "Maciej W. Rozycki" <macro at linux-mips dot org>
- Date: Fri, 7 Dec 2007 15:36:05 +0000 (GMT)
- Subject: Re: Target-specific command logging facility
- References: <Pine.LNX.4.61.0711291525550.3161@perivale.mips.com> <m3tzn4kj7w.fsf@codesourcery.com> <Pine.LNX.4.61.0711291837460.3161@perivale.mips.com> <Pine.LNX.4.61.0712071459300.31587@perivale.mips.com> <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