>Hmm, in addition to /dev's suggestions, why not put the program under >the
>debugger as soon as the crash occurs to see exactly what has caused the
>crash, and likely obtain some call stack and variable value snapshots?
I tried putting a breakpoint in there but the debugger refused to accept it... I'll see if I can indeed debug once it crashes - why didn't I think of that? {:v)
Nope, won't have it - says "PID invalid" and then bombs out.
Start your app. Start msvc. Attach to the process, it will soft-break it. Then tell it to run. When it GPFs it will already be in the debugger.
_______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
