Rich Healey ri...@psych0tik.net added the comment:
I looked into it a bit further.
With some trial and error I narrowed the source of the problem to be the
'KernelModeDriverInstall' option under compatibility. I believe this
isn't a problem, because python shouldn't be trying to install
Rich Healey ri...@psych0tik.net added the comment:
I've done some more fiddling with the debugger, once I discovered the
Windows symbol servers, and a tool called application verifier some
things started to fall into place.
LuaPriv takes care of user privelidges, the program runs fine when I
Rich Healey ri...@psych0tik.net added the comment:
I have an apology to make for wasting your time.
Further investigation demonstrates that it was evidently fiddling with
the Application Verifier that broke everything (although I installed it
during my debugging attempts- I'm guessing
Rich Healey ri...@psych0tik.net added the comment:
Download the debugging suite from
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx#
Open windbg
Press Ctrl + E to load an executable
Select your python binary
Step through by typing g in the text box at the bottom
Rich Healey ri...@psych0tik.net added the comment:
Carey I can send you the steps I used to create the dump if you like so we
can check if it's the same issue?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
Rich Healey ri...@psych0tik.net added the comment:
By running the python.exe (either by double clicking it, typing it's
path into a cmd shell or by opening it in a debugger).
I tried to create a 64 bit build of the source tree which DID start, but
the hoops I had to jump through to build
Rich Healey ri...@psych0tik.net added the comment:
Nope- 2.6.4 fails in the same way.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7206
Rich Healey ri...@psych0tik.net added the comment:
They did at first for me, and then something changed.
They now don't start. I don't have the skills to properly diagnose why,
all I can get out of my debuggers is that something is happening in
ntdll.dll
Not necessarily pointing fault
New submission from Rich Healey ri...@psych0tik.net:
64 bit pythons fail on 64 bit Windows 7.
The crash happens with python 2.6 and 3.1 in 64 bit mode. 3.1 was a
clean install after the issue presented itself.
I'm not 100% sure how best to help with the problem, I've attached the
dump from
Rich Healey ri...@psych0tik.net added the comment:
I'm not 100% sure.
I have a x64 machine running Windows 2008. I will check if it's in the
log now.
I will also check if it's in the debug trace for x86 python (which works).
RESULTS:
I get the LuaPriv initialised line on x86 python on my
Rich Healey ri...@psych0tik.net added the comment:
I think that dump may be incorrect because it does not have all the
symbols. I will checkout source for latest 3.x trunk and attempt to
build 64 bit binaries.
--
___
Python tracker rep
Rich Healey ri...@psych0tik.net added the comment:
No action- the interpreter fails to start.
Or do you mean what changed to make it break? I'm not sure. It used to
work but I don't believe I changed anything on my system.
--
___
Python tracker rep
12 matches
Mail list logo
