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

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 a stack trace.

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

Have you tried using PTVS and attaching to process with the Python debug engine enabled? Then you can set a breakpoint in managed code and look for calls to sys.exit On Sat, Aug 27, 2016 at 7:23 AM Bob Hood wrote: > On 8/25/2016 9:36 PM, eryk sun wrote: > > On Fri, Aug 26,

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

On 8/25/2016 9:36 PM, eryk sun wrote: On Fri, Aug 26, 2016 at 12:42 AM, Bob Hood wrote: Any suggestions as to how I could determine the cause of the crash without having to uninstall ALL of my software? Configure a postmortem debugger [1] (e.g. windbg -I). Use gflags to