> > Nope, won't have it - says "PID invalid" and then bombs out. > > Hmm, I've never seen this problem occur... Is the process > already terminated > when you try to debug it?
Not sure how to answer that - using XP, it comes up with a standard (for XP) crash dialogue that has a Debug button to try and attach to it and debug, that's what caused that invalid PID problem. Could that message possibly be caused if the crash occurred in the worker thread rather than the main thread? >What happens if you start the app from > within VC > studio, and then let it run with no breakpoints until it crashes? Curious - it does break into the code, but it seems it has gone awry in the middle of DllUnregisterServer()! Why would it end up there?! Here's the stack: MyCommsDLL! DllUnregisterServer + 2708 bytes MyCommsDLL! DllUnregisterServer + 65966 bytes KERNEL32! 7c80b50b() and here's the offending assembly code: 02CC1E22 xor ebx,ebx 02CC1E24 mov ecx,dword ptr [esi+0Ch] <==== Here 02CC1E27 push edi 02CC1E28 push eax 02CC1E29 push ecx -- Jason Teagle [EMAIL PROTECTED] _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
