possible bug, ui flow - raddbg wants to display/step into debugger_jmc.c
This happens when I am stepping into function calls that take me to other files in my project. The debugger wants to display debugger_jmc.c
If i use the "find alternative" button to point at a copy of this file, it will still step into this file and not skip it.
I used this copy of debugger_jmc.c that I found to tell raddbg where to look. https://github.com/ojdkbuild/tools_toolchain_vs2017bt_1416/blob/master/VC/Tools/MSVC/14.16.27023/crt/src/vcruntime/debugger_jmc.c
The debugger now steps thru this file as expected and continues to work, but this takes 5 steps each time, and the expected ui flow would be to directly step into the function, bypassing debugger_jmc.c
Windows 11 exe compiled with msvc 1943 raddbg 0.9.21 built locally
It should be correctly avoiding those calls, I will need to check why it isn't, but how are you building your executable? I don't think this JMC feature is on by default. I will look at why the debugger is not correctly ignoring them now, but to mitigate the issue you can also just remove the /JMC option from your build line.
I am using premake to generate build files and either building within Visual Studio, or directly with this command line call to msbuild.
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\msbuild.exe" MySolution.sln -p:Platform=x64 -p:Configuration=Debug -nologo -v:q -p:WarningLevel=4 -maxcpucount
It seems that premake sets the JMC flag by default for debug builds. I was able to just tell premake to not set the flag within my Debug configuration with the command justmycode "Off"
Doing this has resolved my issue, thanks!