Version 3.1.3 fails on every run

[TheVoidBeing]

As the title says, every time I run the newest version of netcoredbg, it loads some dll's then fails.
Though I can only get it to load dll's with the --log flag, else it shows nothing.

I tried logging with --log=file and got this:

0.000 I/NETCOREDBG(P23024, T23236): main.cpp: main(444) > Netcoredbg started
0.000 I/NETCOREDBG(P23024, T23236): main.cpp: instantiate_protocol(128) > Creating protocol CLIProtocol
0.000 I/NETCOREDBG(P23024, T23236): main.cpp: main(493) > pidDebugee 0
0.000 I/NETCOREDBG(P23024, T18312): ioredirect.cpp: worker(164) > worker started
2.031 E/NETCOREDBG(P23024, T23236): ioredirect.cpp: async_input(416) > expression '!input_handle' failed: can't issue read request for real stdin
2.142 F/NETCOREDBG(P23024, T23236): main.cpp: operator(446) > Netcoredbg is terminated due to call to std::terminate: see stderr..

I tried both of the following with and without --log=file:

netcoredbg -- dotnet <path/to/project/dll>

and:

netcoredbg --interpreter=cli -- dotnet <path/to/project/dll>

I am running with a windows computer, if that could make a difference.

Edit: just remove -test from second command, have it renamed to not conflict with 3.1.2

[gbalykov]

Please share your build command. Does it work for you in non-cli mode?

[TheVoidBeing]

I just use the normal dotnet build, nothing else.

I have not tried non-cli mode, as I only use helix/terminal for coding. I don't even know how to.

[gbalykov]

You can try --interpreter=mi or --interpreter=vscode instead of cli. Both are less convenient to use manually, but this could be enough to check whether issue is in cli or not.

[TheVoidBeing]

I just tried with both in the CLI.

mi responds with a lot of ^error,msg="Failed to parse input"
vscode just hanged, with nothing changing when I wrote something.

I assume I'm just doing it wrong, but as said before: I don't know how these work.
I'll try looking it up.

[viewizard]

Could you please provide more information about your Windows version and what terminal you are using?

[TheVoidBeing]

The terminal I use is the Terminal app from the Microsoft store, running the default CMD version.
My Windows is 11 Enterprise with 24H2.

If anything is missing please let me know.

[viewizard]

Hmm... look like some issue, in case I start debugger debug build on Windows 11:

D:\projects>D:\projects\netcoredbg\bin\netcoredbg.exe --interpreter=cli -- dotnet D:\projects\TestAppWinFormsStackTrace\bin\Debug\net10.0-windows\TestAppWinFormsStackTrace.dll
ncdb> r
Assertion failed: !read_lock, file D:\projects\netcoredbg\src\utils\ioredirect.cpp, line 404

Looks like #160 again... but for Windows 11 now.
Need more time for investigation. Looks like Windows 11 have some changes and debugger build with old Windows 10 SDK don't work proper any more.

[TheVoidBeing]

In that case I will just stick with 3.1.2 until new news about this comes out