This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] visualizing locals and backtrace in debug session
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Serge Voilokov <voilokov at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 25 Apr 2013 05:45:43 +0300
- Subject: Re: [PATCH] visualizing locals and backtrace in debug session
- References: <CAJyvAALrYcy68tjM2+8yb5ufdAmbkL3jaOYDWCdOyS5ddhqtsQ at mail dot gmail dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Serge Voilokov <voilokov@gmail.com>
> Date: Wed, 24 Apr 2013 16:37:18 -0400
>
> This patch adds new post hooks which dump registers, stack, local
> variables on each step, next, run, finish command.
Thanks!
> Output goes to ~/gdbout.txt file where can be watched by 'tail -f
> ~/gdbout.txt' command in the separate terminal.
This is unlike anything GDB does. I might understand an option to
direct this to a file (although we already have a command to send all
output to a log file gdb.txt), but doing this _only_ to a file?
Sounds like a wrong way to me.
> 2013-04-24 Serge Voilokov <voilokov@gmail.com>
>
> New command 'auto_enable' which sets post hooks on run, step, next
> and finish commands. Hooks dump registers, stack, local variables into
> ~/gdbout.txt file which can be watched by 'tail -f ~/gdbout.txt'.
> * NEWS: New 'auto_enable' command for visualizing runtime info.
> * data-directory/Makefile.in: Add gdb/command/auto_info.py
> * data-directory/Makefile.in: Add gdb/command/auto_info.cmd
> * python/lib/gdb/command/auto_info.py: Implemention of the 'auto_print'
> command using the GDB Python API.
> * python/lib/gdb/command/auto_info.cmd: Register post hooks for run,
> step, next and finish commands which calls auto_print.
I don't see the NEWS part in your patch. And new commands require a
suitable change to the manual.
Thanks again for working on this.