Re: Always disable pagination with MI?

[Vladimir Prus <vladimir@codesourcery.com>]

Pedro Alves wrote:

> A customer noted that sometimes, when GDB failed to evaluate
> a watchpoint's condition, GDB would leave the inferior
> stopped, but would forget to output a *stopped notification.
> Something like this:
> 
>  gdb -i=mi ...
>  ...
>  (gdb)
>  &"Error in testing breakpoint condition:\n"
>  &"Cannot access memory at address 0x0\n"
>  ~"Hardware watchpoint 2: global2\n"
>  ~"\n"
>  
>  ~"Old value = 1\n"
>  ~"New value = 2\n"
> 
> And nothing else came out.  What was really happening, is
> that pagination kicked in at this point, because no pagination
> prompt is visible.  If one presses enter when this happens,
> the rest of the expected output, along with *stopped actually
> comes out:
...
> Whoops.  I tried this on 6.8 and 7.0 and they behave
> the same.  This was probably never right, and I gather that
> most frontends must be disabling pagination
> already: either by explicit "set height 0"/"set pagination off",
> or implicitly by running GDB from a non-tty, and, those that
> want pagination handle it themselves.

Yes, I think that's what frontends do.

> 
> Any objections to this?
> 

Seems reasonable, FWIW.

- Volodya