[Bug tui/9845] Multiple line displays may generate a false command

[Stephane.Carrez at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=9845

Stephane Carrez <Stephane.Carrez at gmail dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |Stephane.Carrez at gmail
| |dot com

--- Comment #1 from Stephane Carrez <Stephane.Carrez at gmail dot com> 2012-11-10 13:59:36 UTC ---
There is the same behavior in non TUI mode (check on gdb 7.5.50).

Any 'display' command that executes and requires a prompt_for_continue
will prevent the previous command from being executed on \n.

The problem appears more in TUI mode due to the small command window.

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-09-02
CC| |tromey at sourceware dot org
Ever confirmed|0 |1

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
First, this is actually the documented behavior:

GDB can also use <RET> in another way: to partition lengthy output,
in a way similar to the common utility 'more' (*note Screen Size: Screen
Size.). Since it is easy to press one <RET> too many in this situation,
GDB disables command repetition after any command that generates this
sort of display.


That said, I think it would be fine to add a setting so that this
can be controlled.

[palves at redhat dot com]

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

Pedro Alves <palves at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com

--- Comment #3 from Pedro Alves <palves at redhat dot com> ---
I've often thought that using <SPACE> for 'more' would be better/safer than
<RETURN>.