codelldb Debugging breaks

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)

Dec 18 '24 21:12 foofel

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)

Dec 20 '24 02:12 vadimcn

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.

Dec 20 '24 14:12 foofel

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

Dec 20 '24 16:12 vadimcn