Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pagination of long output is not properly handled #145

Closed
xuhdev opened this issue Oct 2, 2017 · 3 comments
Closed

Pagination of long output is not properly handled #145

xuhdev opened this issue Oct 2, 2017 · 3 comments

Comments

@xuhdev
Copy link

xuhdev commented Oct 2, 2017

For long output, cgdb seems not able to handle the pagination. For example,

#include <vector>

int main()
{
    std::vector<std::vector<int> > x(10);
    x[0] = {1, 2, 3};
    x[1] = {4, 5, 6};
    x.push_back({2, 3, 4});
}

At the end of the main function, p x gives a really long output (with

set print array on
set print pretty on

in ~/.gdbinit), but no pagination is available, even if gdb has the pagination option on.

@brasko
Copy link
Contributor

brasko commented Oct 6, 2017

Yes, CGDB turns off pagination because it uses the a2 interface to communicate with gdb still.

I'm working towards removing the a2 communication pieces and moving purely towards mi.
Actually, this work is quite close. However, it may be months before I have this completed.

When this work is done, I believe pagination will work as expected. That is, the same as on the
command line just using gdb.

@brasko
Copy link
Contributor

brasko commented Mar 1, 2021

This should be fixed in the new-ui branch. Please let me know. Thanks.

@brasko
Copy link
Contributor

brasko commented Mar 6, 2021

Should be fixed in master

@brasko brasko closed this as completed Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants