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

[DSF-GDB] Python input from debugger console is not treated as secondary prompt #362

Open
DavidCosmin opened this issue Apr 12, 2023 · 1 comment
Labels
debug The debug components of CDT, anything to do with running or debugging the target. featurerequest A new feature or enhancement

Comments

@DavidCosmin
Copy link

Describe the bug
When running a GDB python input command from debugger console, the line inputted is not treated as secondary prompt, thus, because it is not processed with RawCommand, the string "token-interpreter-exec console" is added to the input.

image

Expected behavior
I would have expected that the input line should be secondary prompt.
Eg.
image

Desktop:

  • OS: Windows 10

Build Identifier:

  • Eclipse version: 2022-06 (4.24.0)
  • Build id: 20220609-1112
  • GDB version: 9.2 (but tried with 8.x and 7.x as well)
@jonahgraham
Copy link
Member

Thanks for the bug report. The best solution for this will be implementing new-ui on Windows like it is on Linux. That would provide a proper and full CLI environment to the user like this:

Peek 2023-04-14 11-00

@jonahgraham jonahgraham added debug The debug components of CDT, anything to do with running or debugging the target. featurerequest A new feature or enhancement labels Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug The debug components of CDT, anything to do with running or debugging the target. featurerequest A new feature or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants