CodeLLDB fails to redirect output to integrated terminal on Windows

[vadimcn]

Yes, sorry for no OS specified.

As for the reproduction I'll try someday to install a fresh vscode without any unnecessary extensions.

I did notice in the log, that it uses some LLVM dll installed on my machine, and not the one you supply in your extension. Worth investigating?

Launching adapter
liblldb: C:\Program Files\LLVM\bin\liblldb.dll

Originally posted by @KucaKun in #1350

[vadimcn]

Let's continue here, looks like this problem is distinct enough from the the original report.

liblldb: C:\Program Files\LLVM\bin\liblldb.dll

Did you configure an alternate backend? Check if you your workspace or folder settings contain "lldb.library": ....
Normally you don't do this, unless there's a specific reason to use an external LLDB instance.

[KucaKun]

Ok, this setting was set, probably due to some experimenting in the past when I tried to resolve the #1350.

I've checked all the variables and the summary is this:

• setting the lldb.library to a dir with LLVM-21.1.6 downloaded from it's github releases makes for a completely empty terminal, but the breakpoints work
• the shell integration, as stated in codelldb-launch fails to connect #1350, needs to be disabled or i get the error stated in that issue, but only on the first run in that terminal, the next runs work as expected. The debug output is visible in the extension verbose logs in the output tab. They just don't get redirected.
• the windows firewall rules on localhost do nothing to those issues

I have updated a comment on the #1350 not to spread misinformation.