On 8/27/2016 12:02 PM, eryk sun wrote:
On Sat, Aug 27, 2016 at 2:19 PM, Bob Hood <bho...@comcast.net> 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.
I kowtow before you, Sir Eryk! :)
Breaking on that function produced the following stack trace:
...
ModLoad: 000007fe`f9410000 000007fe`f9414000
C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
ModLoad: 000007fe`f5450000 000007fe`f547e000 C:\Windows\system32\twext.dll
ModLoad: 00000000`04590000 00000000`04597000
C:\Windows\system32\pythoncomloader27.dll
ModLoad: 00000000`6fff0000 00000000`70093000
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll
ModLoad: 00000000`1e200000 00000000`1e294000 C:\Windows\system32\pythoncom27.dll
ModLoad: 00000000`078c0000 00000000`07baf000 D:\TortoiseHg\python27.dll
ModLoad: 00000000`1e7a0000 00000000`1e7c6000
C:\Windows\system32\pywintypes27.dll
Breakpoint 0 hit
ntdll!RtlExitUserProcess:
Since it is written in Python, the TortoiseHg (Mercurial) install's Python DLL
was being picked up BEFORE my stand-alone Python install. This caused some
kind of incompatibility with the pywin32 install, and the pywintypes27 module
performed an exit(). After renaming the TortoiseHg folder to remove that
incompatible Python version from visibility, the shell extension works perfectly.
Thank you (and everybody) for the pointers. This has been a thorn in my side
for a long time.
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
