Using WinDBG has been going along ok. Step in step out, moving around the stack, setting the breakpoints works well enough.
Some things seem way way wrong.
- error messages on watching some variables, suggesting they are either out of scope, or have illegal/ unitialized values. In many of these cases, the program worked just fine.
- non watchable variables that display "optimized out" when I try to click and inspect them.
I haven't built with robust debug and gdb compile time helper flags- if any such exist. That's next up.
- Setting environment variable CLIENT_CFLAGS=-DDEBUG at the msys command line may enable a bunch of the debug diagnostic messages.