You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On gdb shell, print <var_nam> must wait for user to press enter for more and q for quit and c for continue to print till end. But not happening .
It seems like by default it acting like it assuming user typed c(continue). So it prints the whole object on gdb shell . So had to scroll up to see from start.
And is impossible when tui mode is in or Ctrl x + a .
Kindly provide options (or suggest):
to wait for user to enter continue and
press enter to go line by line.
Previously, I disabled the pagination just during the rendering, but it didn't work well with macOS (for whatever reason).
With my current GDB version (13.2) instead it seems that pagination doesn't affect the dashboard anymore, so I guess I can just get rid of that altogether. But I need to experiment further...
In the meanwhile, try to kill the above line in your .gdbinit.
PS @vs97849 please don't mention random contributors, it's unnecessary noise.
As a side note, since the dashboard (by default) discards the terminal's scrollback buffer, it's quite convenient to just scroll back, since there will not be a lot of content.
On gdb shell, print <var_nam> must wait for user to press enter for more and q for quit and c for continue to print till end. But not happening .
It seems like by default it acting like it assuming user typed c(continue). So it prints the whole object on gdb shell . So had to scroll up to see from start.
And is impossible when tui mode is in or Ctrl x + a .
Kindly provide options (or suggest):
to wait for user to enter continue and
press enter to go line by line.
@rcaputo @lucianposton @Reinis @braiden
@cyrus-and @ProfDiesel @clint4cake @10110111 @cs01
@ccalmels @Quinny @xeyownt @javier-cabezas @jannewulf @lucianposton @A
The text was updated successfully, but these errors were encountered: