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

Debugging breaks #1193

Open
foofel opened this issue Dec 18, 2024 · 3 comments
Open

Debugging breaks #1193

foofel opened this issue Dec 18, 2024 · 3 comments

Comments

@foofel
Copy link

foofel commented Dec 18, 2024

OS: Manjaro on 6.12
VSCode version: 1.95.3
CodeLLDB version: 1.11.1
Compiler: rustc 1.83.0 (90b35a623 2024-11-26)
Debuggee: rust executable

Debugging via f5 starts a new process in a terminal window. The Problem is if there is already some input in the terminal prior to launching the debugging session, then lldb-code tries to run someting like PREV_STUFF /home/XXX/.vscode/extensions/vadimcn.vscode-lldb-1.11.1/adapter/codelldb terminal-agent --connect=37797 it does not clear the clear the terminal input before running the command. This can be reproduced by just running a debug session multiple times. For me VSCode opens up up to 3 debug session terminals. Just type something in all of them and run a debugging session again. (this results in a hanging process hogging 100% cpu)

@vadimcn
Copy link
Owner

vadimcn commented Dec 20, 2024

This is a VSCode issue.
You can try lldb.terminalPromptClear setting to mitigate this (the manual is incorrect about the default value - it's null in the current version)

@foofel
Copy link
Author

foofel commented Dec 20, 2024

Thanks for your replay, it seems like not many people have this problem as there is not much activity :/ I tried to use "lldb.terminalPromptClear". Sadly it looks like vscode is using a different terminal to run the clear commands than the one where it send the debug run command to. So another terminal is cleared.

@vadimcn
Copy link
Owner

vadimcn commented Dec 20, 2024

VSCode must have changed terminal behaviors since this was implemented. Sorry, I've no other suggestions.

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

2 participants