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

[Bob Hood]

On 8/25/2016 9:36 PM, eryk sun wrote:
> On Fri, Aug 26, 2016 at 12:42 AM, Bob Hood <bhood2 at comcast.net> 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
> temporarily enable full page-heap verification for Explorer.
>
> [1]: https://msdn.microsoft.com/en-us/library/ff551063

Thanks, Eryk.  Since I had VS2013 installed already, I tried that first, 
installing the Python extension, running explorer.exe, and then attaching to 
the process.  When I activated the extension from the context menu, the 
Explorer process simply terminated with a 1 exit code.  To be sure, I also 
tried from within windbg.exe, setting the gflags.exe as you pointed out, and 
the same behavior happened.

 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.

What I will probably have to do is start from a pristine Explorer, add in each 
of the extensions I'm currently using, running the Python extension in between 
each install, to try and pin it down.  This is not going to be an easy process.