Suppose that
(gdb) print *this
resulted in 20 lines of output. Yes, there would be Type <return> to continue, or q <return> to quit
, but I'd like to scroll back to the top after I got to the bottom of the output.
I don't think http://sourceware.org/gdb/onlinedocs/gdb/TUI-Keys.html answers my question. It states
<PgUp>
Scroll the active window one page up.
but when the focus is on the command window, PgUp rewinds the command history, instead of scrolling back in the command window. Is it only me who suffers from this behavior?
I'm using PuTTY in order to SSH to Red Hat Linux (if this makes any difference).
One way to see the GDB output history in TUI mode is to enable logging:
set trace-commands on
set logging on
and then tail the log in another shell:
cd where/gdb/is/running
tail -f gdb.txt
This has the advantage of separating scrolling from command interaction, so you can type commands while viewing some past section of the GDB output.
None of the scrolling keys work in my CMD window, so GDB effectively consumes and destroys its own output. Switching out of TUI mode allows me to scroll up, but the output that occurred while in TUI mode is not there--the non-TUI window only shows new output generated after switching out of TUI mode. So far log and tail is the only solution I can find.
Edit: if you activate GDB logging (via set logging on
) before switching to TUI mode, you may find that the logging stops upon entering TUI (this is a bug in GDB). You can toggle it back on:
set logging off
set logging on