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

[eryk sun]

On Mon, Aug 29, 2016 at 12:08 AM, Bob Hood <bhood2 at comcast.net> 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 stack frames back based on the current stack and
instruction pointers (e.g. rsp and rip for an x64 ISA). The default is
up to 20 frames if a frame count isn't specified. Another starting
point when diagnosing a crash is `!analyze -v` [2] to get a verbose
summary of the exception, but that doesn't apply in your case.

[1]: https://msdn.microsoft.com/en-us/library/ff551943
[2]: https://msdn.microsoft.com/en-us/library/ff562112