Skip to content

User input in gdbgui #336

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

Closed
shrinivas96 opened this issue Jun 29, 2020 · 2 comments · Fixed by #346
Closed

User input in gdbgui #336

shrinivas96 opened this issue Jun 29, 2020 · 2 comments · Fixed by #346

Comments

@shrinivas96
Copy link

shrinivas96 commented Jun 29, 2020

Is your feature request related to a problem? Please describe.
Hello. This may be a very trivial thing that only I am unable to do. I am sure what I am about to ask already exists and only I am not able to find it. It is also possible that this question/request is at the wrong place. Please point me in the right direction if that's the case.
My doubt/question: (C++) How do I enter a keyboard input when I reach a cin >> var; in my code? There doesn't seem to be a way to enter that value while using the GUI. I am able to enter a value when I use the cli at the bottom of the browser page that says:
(gdb) enter a gdb command. To interrupt inferior, send SIGINT. I have to do the r and then n to get to that part. But I can do this in gdb from terminal as well.

Describe the solution you'd like
A field that can get activated when it recognises that the program is waiting for a user input?

Describe alternatives you've considered
NA

Additional context
NA

@cs01
Copy link
Owner

cs01 commented Jun 29, 2020

See the section on redirecting cli output https://www.gdbgui.com/faq/

If you redirect output it should behave more like you expect.

@cs01
Copy link
Owner

cs01 commented Aug 23, 2020

A new terminal dedicated to I/O has been added to the frontend in gdbgui v0.14.

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

Successfully merging a pull request may close this issue.

2 participants