On 29 August 2010 10:03, Chris Withers <chris@simplistix.co.uk> wrote:
Tim Hoffman wrote:
on linux
timh@chrome:~$ file /usr/bin/python2.5 /usr/bin/python2.5: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped timh@chrome:~$
Right, so the linux boxes are 32-bit as I suspected:
$ file /usr/local/bin/python2.6 /usr/local/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped
$ file /usr/local/bin/python2.6 /usr/local/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
os/x will work the same.
Sadly not:
$ file /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6: Mach-O universal binary with 2 architectures /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (for architecture ppc): Mach-O executable ppc /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (for architecture i386): Mach-O executable i386
This is telling you that the executable contains versions for ppc and i386 (no x86_64, so no 64bit version). Another way to confirm this is at the python prompt with: import sys; sys.maxint
Nonetheless, why would a .zexp on a 32-bit architecture and import on 64-bit cause sudden crash death when viewing /manage_main of a an imported folder containing Page Templates?!
Still in "wtf?!" mode...
Your best bet is adding the breakpoint and stepping through with pdb until you hit the error (you can usually just hold down the return key after the first step...) Laurence