Re: [python-win32] win32com.server failure: Is debugging possible?

On Mon, Aug 29, 2016 at 12:08 AM, Bob Hood wrote: > Breaking on that function produced the following stack trace: I'm glad you found the culprit, but actually the "ModLoad" lines are just printed by the debugger as DLLs are loaded. The stac[k] trace [1] attempts to walk the

Re: [python-win32] win32com.server failure: Is debugging possible?

On 8/27/2016 12:02 PM, eryk sun wrote: On Sat, Aug 27, 2016 at 2:19 PM, Bob Hood wrote: From what I can tell, it's not actually a crash. It appears to be an exit() with a result of 1, so it's not going to be easy to track down. Break on ntdll!RtlExitUserProcess to print