[Bug cli/8822] log commands along with their output

[Bug cli/8822] log commands along with their output

[ppluzhnikov at google dot com]

------- Additional Comments From ppluzhnikov at google dot com  2010-01-22 17:00 -------
*** Bug 11204 has been marked as a duplicate of this bug. ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppluzhnikov at google dot
                   |                            |com


http://sourceware.org/bugzilla/show_bug.cgi?id=8822

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug cli/8822] log commands along with their output (make logging

[ppluzhnikov at google dot com]

------- Additional Comments From ppluzhnikov at google dot com  2010-01-22 17:06 -------
>From PR 11204:
---
It would also be nice to be able to timestamp output in gdb.txt, so when
dealing with performance bugs, it's immediately clear which operations
took how long.

I think 'set logging NNN' could become a multi-state (similar to 'handle'), e.g.

 set logging user gdb timestamp  # turn all on
 set logging on             # alias for "set logging gdb" (backward compat)
 set logging off            # alias for "set logging nouser nogdb notimestamp"
---

The advantage of GDB logging over script(1) is that it eliminates "line noise"
-- all the ^R and ^H that make script log hard to read and understand.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at sourceware dot|ppluzhnikov at google dot
                   |org                         |com
            Summary|log commands along with     |log commands along with
                   |their output                |their output (make logging


http://sourceware.org/bugzilla/show_bug.cgi?id=8822

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug cli/8822] log commands along with their output (make logging more flexible)

[ppluzhnikov at google dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|log commands along with     |log commands along with
                   |their output (make logging  |their output (make logging
                   |                            |more flexible)


http://sourceware.org/bugzilla/show_bug.cgi?id=8822

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug cli/8822] log commands along with their output (make logging more flexible)

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=8822

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #8 from Tom Tromey <tromey at sourceware dot org> ---
I was going to suggest trace-commands today, but I see it's been done.
I wonder if a new logging mode could print the prompt and the
command instead of the "+".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug cli/8822] log commands along with their output (make logging more flexible)

[vries at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=8822

--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #8)
> I was going to suggest trace-commands today, but I see it's been done.
> I wonder if a new logging mode could print the prompt and the
> command instead of the "+".

Using this:
...
diff --git a/gdb/cli/cli-script.c b/gdb/cli/cli-script.c
index 5f81db418bc..6a59607aa47 100644
--- a/gdb/cli/cli-script.c
+++ b/gdb/cli/cli-script.c
@@ -495,8 +495,13 @@ print_command_trace (const char *fmt, ...)
   if (!source_verbose && !trace_commands)
     return;

-  for (i=0; i < command_nest_depth; i++)
-    gdb_printf ("+");
+  if (0)
+    {
+      for (i=0; i < command_nest_depth; i++)
+       gdb_printf ("+");
+    }
+  else
+    gdb_printf ("%s", get_prompt ().c_str ());

   va_list args;

...
I get:
...
$ gdb -q -batch -ex "set trace-commands on" -ex "inferior" -ex "set prompt
(bla) " -ex "inferior"
(gdb) inferior
[Current inferior is 1 [<null>] (<noexec>)]
(gdb) set prompt (bla) 
(bla) inferior
[Current inferior is 1 [<null>] (<noexec>)]
...

Doesn't take into account annotations though, for that we need top_level_prompt
instead.

-- 
You are receiving this mail because:
You are on the CC list for the bug.