Changes between Initial Version and Version 1 of Ticket #152, comment 3
- Timestamp:
- Dec 14, 2015, 1:11:51 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #152, comment 3
initial v1 1 I also checked i686 binaries here (by unpacking the python DLL and EXE manually and playing with them). 1 I also checked i686 binaries here (by unpacking the python DLL and EXE manually and playing with them) — they work. 2 3 I suppose you have the new python installed after this failure anyway. Can you check if it works per se, by starting some simple python script with `C:\usr\bin\python2.7.exe`? 2 4 3 5 The `Interrupted system call` thingy actually looks like a rare and old LIBC bug which isn't completely fixed ATM (see http://trac.netlabs.org/libc/ticket/256), but it's a completely wild guess so far. It could be the case if python were using multiple threads for something and were trying to kill one of them for some reason but I have no knowledge about how and when python uses threads.