Hi Chris file command run on any binary (lib, executable will tell you) 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:~$ os/x will work the same. Rgds T On Sat, Aug 28, 2010 at 3:53 PM, Chris Withers <chris@simplistix.co.uk>wrote:
Tres Seaver wrote:
Now, how in gdb do I find out what it was that was trying to be imported? (should any sort of import cause a core dump?!)
Things you learn, thanks for that :-)
Okay, another interesting data point; this appears to be related to OS. The originating server is a 32-bit (I think, how can I double check?) linux box, the crashing machine is my 64-bit (but I'm pretty sure python is 32-bit, how can I check?) MacBook Pro.
I tried importing the .zexp back onto the originating server; no crashes.
I tried importing the .zexp onto my linux dev both; no crashes.
This ring any bells for anyone?
Chris
-- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )