[Bug tui/17849] Showing local variables in gdb tui window

["ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

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

Hannes Domani <ssbssa at sourceware dot org> changed:

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

--- Comment #9 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Paul Buxton from comment #8)
> It looks like Hannes implementation is much more complete and polished.
> Mine was mostly just a weekend experiment. I do think there is value in
> having a variables window 'disconnected' from display behaviour though. My
> watches window (which might be confusingly named) maintains it's own list
> of statements to parse_and_eval. If others think this is worthwhile I would
> be happy to update it and send it in for contribution?

At first I also didn't use the display variables, and instead had a 'watch'
window, and corresponding commands 'watch-add' and 'watch-del', very similar to
yours.
The main reason I changed this to the display variables was that you don't need
to remember new commands.
Also, the display command knows which frame an expression belongs to.

But it would be easy to re-add the watch window, I just need to derive it from
the VariableWindow class, containing a variables() function which returns the
statements+values.
I already had this kind of stuff in mind, in case someone wanted multiple watch
windows, or other custom variable windows (like if you are in a python frame,
show the local python variables).

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