extern "C" void __stdcall Entry();
When I press f11 to start/step into, It gives the message "Entry point procedure was not found!", and does not break.
I'm working around it by using "fbreak Entry", but it is a bit tedious to type every time I start debugging.
Is there some easier way in the current build to break at entry?
I thought saving the current session might save the breakpoint, but I can't figure out how to load the session again.
Thanks for doing this project, it has been great to use.
A few smaller things:
When launching the debugger from a director that is not the directory where the debugger is installed, the launch settings paths are not correctly set:
Executable Path = C:\Dev\Game_Project\Files\cdbg\cdbg64.exe"
Working Directory = C:\Dev\Game_Project\Files\cdbg\
This path doesn't exist; it is the install dir path being over written by the path the debugger was launched from.
The launch path is "C:\Dev\Game_Project", and the install path is "C:\Program Files\cdbg".
They have been fused into one Frankenstein's path "C:\Dev\Game_Project\Files\cdbg\".
It looks like you forgot to update the string length or null terminator or something.
Another thing, when exiting the program while the debugger is attached, it panics on invalid code path,
file "w:\\dbg\\code\\win64_tracer.c", line 1391.
Also, the debugger used to prompt me to select an executable at launch, but it seems to have stopped doing that now.
I don't know if you updated it since last time I downloaded it. I just thought I'd mention it, because the behavior had changed but the version number hadn't.