Mikhail Kurinnoi
Mikhail Kurinnoi
You should be able to enable protocol logging in launch.json with: ``` "logging": { "engineLogging": true }, ``` for example: https://github.com/Samsung/netcoredbg/issues/155#issuecomment-1879644599
Looks like `async` methods should care about exceptions in another way: ```
We also faced with terminal-related (CLI related) issues in debugger work on Windows in case it build with latest MSVS 2022 versions. Probably, also related to this issue. Our current...
Interesting, thanks for the info.
Not in plans for now. Btw, could you please provide vsdbg part of vscode protocol log with "launch" request you need?
> I set a breakpoint on if(! cin.good()) at method std::string VSCodeProtocol::ReadData(), I can see my initialize request in the cin. As I see, debugger execute code inside `!cin.good()` code...
@fenixjiang you could find working C# example here - https://github.com/Samsung/netcoredbg/tree/master/test-suite Our test suite framework aimed to network and local interaction with debugger by VSCode and MI/GDB protocols. For example, VSCode...
We definitely will not add some code just because this change behavior in the way you need. I don't see any reason for `cout.clear();` line here. The point is -...
I updated upstream sources, it should support Windows 10 x86 now. Could you please confirm, that you still have this issue with latest sources?
Note, we support Hot Reload feature for Tizen OS only, since it required custom runtime build + you will need generate IL/metadata/PDB deltas somehow, and even for Tizen OS it...