gandalfas
gandalfas
>even without lldb in the picture, the standard input is ignored? actually, in that case, std in and std out are handled just fine by the program on its own....
I added these statements to the top of program: ``` import Foundation // exit() let myStdIn = FileHandle.standardInput let myStdOut = FileHandle.standardOutput let myStdErr = FileHandle.standardError print("myStdIn: \(myStdIn)") print("myStdOut: \(myStdOut)")...
Will do. Meanwhile, I ran ProcMon and after filtering out all unrelated processes, during the 9 seconds after Start Debugging, I have 15,000 lines, all from swiftc (starting the debug...
In short, the Swift handles are equal to the C handles. I added a C DLL to the Swift main prog. Code: ``` HANDLE myStdInputHdlFromC = GetStdHandle(STD_INPUT_HANDLE); printf("myStdInputHdlFromC: %x\n", myStdInputHdlFromC);...
OK thanks, I will experiment with that tomorrow morning. But if I remember correctly, when I remove the setting that points to the custom LLDB, the normal LLDB has correct...
>when running with lldb, you will need to switch windows to the lldb input and press the enter key before the inferior will accept any input. I was able to...
> (Kim said) But if I remember correctly, when I remove the setting that points to the custom LLDB, the normal LLDB has correct behavior in terms of stdin/stdout. I'll...
so to me, either vscode-lldb takes different setup paths when the lldb.library setting exists, or, custom LLDB is handling the VS Code scenario differently than the standard LLDB.
Hi svanimpe. I am having the same error as you reported above. Has your issue been fixed yet? ``` Fatal Python error: initfsencoding: unable to load the file system codec...