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: Tom Tromey <tromey at redhat dot com>
- To: Serge Voilokov <voilokov at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 26 Apr 2013 14:23:17 -0600
- Subject: Re: [PATCH] visualizing locals and backtrace in debug session
- References: <CAJyvAALrYcy68tjM2+8yb5ufdAmbkL3jaOYDWCdOyS5ddhqtsQ at mail dot gmail dot com>
>>>>> "Serge" == Serge Voilokov <voilokov@gmail.com> writes:
Serge> This patch adds new post hooks which dump registers, stack, local
Serge> variables on each step, next, run, finish command.
Thanks for the patch.
Serge> Output goes to ~/gdbout.txt file where can be watched by 'tail -f
Serge> ~/gdbout.txt' command in the separate terminal.
I don't think we want something that works this way. It is not like
anything else gdb does.
Serge> Hooks are disabled by default.
Serge> auto_enable command enables the hooks.
This command name is very un-gdb-like.
I suggest choosing something else.
How do you disable this command?
Serge> +++ gdb/gdb/python/lib/gdb/command/auto_info.cmd 2013-04-24
Serge> 13:58:47.000000000 -0400
Serge> @@ -0,0 +1,15 @@
Serge> +define hookpost-step
Serge> +auto_print
Serge> +end
Defining post hooks seems like something that ought to be reserved for
the user. So if this can't be done using existing Python events, I
suggest adding the necessary events.
I wonder how these interact with non-stop mode.
Tom