Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Command trace testsuite
Date: Mon, 14 Aug 2006 07:32:00 -0000	[thread overview]
Message-ID: <44DC80E3.7000401@st.com> (raw)
In-Reply-To: <uzmece6yt.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

Eli Zaretskii wrote:
> Okay, but...
> I think ``nesting'' is better here.

Thanks, I committed the attached.

Andrew

[-- Attachment #2: commandtrace-news.patch --]
[-- Type: text/plain, Size: 775 bytes --]

2006-08-11  Andrew Stubbs  <andrew.stubbs@st.com>

	* NEWS: Add 'set trace-commands' command.

Index: src/gdb/NEWS
===================================================================
--- src.orig/gdb/NEWS	2006-08-11 13:40:19.000000000 +0100
+++ src/gdb/NEWS	2006-08-11 13:42:30.000000000 +0100
@@ -21,6 +21,12 @@ show substitute-path
   for instance when the sources were moved to a different location
   between compilation and debugging.
 
+set trace-commands
+show trace-commands
+  Print each CLI command as it is executed.  Each command is prefixed with
+  a number of `+' symbols representing the nesting depth.
+  The source command now has a `-v' option to enable the same feature.
+
 * REMOVED features
 
 The ARM Demon monitor support (RDP protocol, "target rdp").

      reply	other threads:[~2006-08-11 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 17:05 Andrew STUBBS
2006-08-08 17:34 ` Daniel Jacobowitz
2006-08-10 16:16   ` Andrew STUBBS
2006-08-10 17:12     ` Daniel Jacobowitz
2006-08-10 19:13       ` Andrew STUBBS
2006-08-10 20:30         ` Eli Zaretskii
2006-08-14  7:32           ` Andrew STUBBS [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=44DC80E3.7000401@st.com \
    --to=andrew.stubbs@st.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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