gandalfas

argg, @adam-fowler , I just saw your comment of yesterday. I did check for any follow-up from you or @compnerd on #301 just before creating this issue 309, but alas,...

I am trying to reproduce Adam's case: >the standard lldb prints directly to the command line any output from the application but I get different results. when I put the...

also, Adam said >If you use the swift lldb it opens up a new window for the output. I'm assuming this difference is what is causing the issue inside vscode-swift...

A thought: since commenting out the "lldb.library" entry in settings.json makes things work as expected (stdout and stdin are in VS Code's 'Terminal' pane), could we assume that whoever is...

> the new window might be the result of AllocConsole yes, agreed, and I believe that is a valid technique to achieve clarity, i.e., when lldb is run as a...

I was able to get the standard LLDB to ignore my python310 folders, by doing: ``` rem PYTHONHOME=C:\Program Files\Python\Python310 rem PYTHONPATH=C:\Program Files\Python\Python310\Lib;C:\Program Files\Python\Python310\Lib\site-packages; set PYTHONHOME=c:\Users\Kim\.vscode\extensions\vadimcn.vscode-lldb-1.7.0 set PYTHONPATH=c:\Users\Kim\.vscode\extensions\vadimcn.vscode-lldb-1.7.0\Lib;c:\Users\Kim\.vscode\extensions\vadimcn.vscode-lldb-1.7.0\Lib\site-packages; ``` This is...

>I think that we should look at how the inferior is launched. I suspect that this might be a bug in lldb-server. One quick test would be to try a...

@compnerd, I see on your ds2 page that I do not have any of the many build tools listed there, and I would really prefer not to install a bunch...

Thank you for that prebuilt 64-bit binary! That save a lot of time and avoided the post-uninstall crud. I ran ds2 per the ds2 github page, and have some partial...

@compnerd and @adam-fowler, Was there anything more I can do to help gather information on this? Or, are we thinking that we can't yet identify which project this should be...