It is not possible to scroll up in the CMD window in TUI mode. Only the SRC window will scroll. Setting focus to the CMD window does not change the problem. All of the following keys are ignored: {PgUp,PgDn,<,>,+,-}, and the up and down arrows traverse the command history. This makes TUI mode substantially useless, because it is not possible to see the output of past values. One can enable logging and tail the log, but the log fails to report the commands from which the output was generated (and therefore the log is overall quite useless). The debugger is only usable when all past session information can be seen by scrolling back to it (and he logging output is only usable when it contains both the commands and the resulting output). GDB 7.4-2012.04 Ubuntu 12.04 kernel version 3.2.0-29-generic x86 PC Thanks for your help with this.
(In reply to comment #0) > but the log fails to report the commands from which the output was generated set trace-commands on Otherwise you are right that readline library does not provide any real terminal, it cares only about the current line. GDB uses 'set pagination on' so that no output is accidentally lost but what is scrolled away is really lost. Maybe you would prefer some other front end besides TUI: http://sourceware.org/gdb/wiki/GDB_Front_Ends
Actually with "set trace-commands on" I can just tail the log. (I searched for a long time trying to find such a setting and did not come up with anything.) The graphical interfaces seem to always be missing essential things, like printing assembly at an arbitrary address, so I will use TUI with logging. It still seems unfortunate that TUI mode is so convenient, yet destroys the output. If it would just work the same as GDB without TUI mode, it would be great.