[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

2012-12-28 Thread Terry J. Reedy
Terry J. Reedy added the comment: Antoine: do you know anything about this message? Fatal Python error: PyEval_RestoreThread: NULL tstate Is there a serious possibility that it could indicate a CPython error, as opposed to an extension author error? Could running Windows on Mac hardware make a

[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

2012-12-28 Thread Antoine Pitrou
Antoine Pitrou added the comment: Well, the error message comes from a misuse of the PyEval_RestoreThread() (by passing it a NULL argument), either directly or by using another API such as Py_END_ALLOW_THREADS which calls that function. The problem is likely to be in the Solidoodle extension.

[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

2012-12-28 Thread Leonardo DaVinci
Leonardo DaVinci added the comment: Terry, I've tried installing on Mac at least 6 times and I still get error messages. I'm dealing with Solidoodle with no success. I have an appointment with a 3d Print Lab on Jan 3rd (50 miles away) to help me resolve my issues. Regards Ciro On Fri, Dec

[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

2012-12-28 Thread Antoine Pitrou
Antoine Pitrou added the comment: I've tried installing on Mac at least 6 times and I still get error messages. I'm dealing with Solidoodle with no success. I have an appointment with a 3d Print Lab on Jan 3rd (50 miles away) to help me resolve my issues. Ciro, it seems you should wait a

[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

2012-12-28 Thread Leonardo DaVinci
Leonardo DaVinci added the comment: Actually Antoine, Solidoodle has sent 2 email replies, 1 was a video link to some British guy opening his box which wasn't packed like mine and had missing parts. and the second email was just as useless stating that maybe I'm running both platforms at the

[issue16749] Fatal Python error: PyEval_RestoreThread: NULL tstate

2012-12-28 Thread Terry J. Reedy
Terry J. Reedy added the comment: OK, given Antoine's reply, I am going to close this until there is actionable information. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16749

[issue16749] Fatal Python Error

2012-12-22 Thread R. David Murray
R. David Murray added the comment: Not really, I'm afraid. You'd have to look at the crash dump in a debugger to get more useful information. Perhaps one of the windows devs will have more concrete advice, I don't use Windows myself. -- ___

[issue16749] Fatal Python Error

2012-12-22 Thread Leonardo DaVinci
Leonardo DaVinci added the comment: Ok I'll try booting and installing in Mac to see if the issue reappears. Thanks for your time. Happy holidays. Ciro On Sat, Dec 22, 2012 at 9:46 AM, R. David Murray rep...@bugs.python.orgwrote: R. David Murray added the comment: Not really, I'm

[issue16749] Fatal Python Error

2012-12-21 Thread R. David Murray
R. David Murray added the comment: Given the error message, my guess would be that there is a bug in the Solidoodle Python extension module. That is, it is unlikely to be a bug in Python. -- nosy: +r.david.murray ___ Python tracker

[issue16749] Fatal Python Error

2012-12-21 Thread Leonardo DaVinci
Leonardo DaVinci added the comment: Ok thanks for the quick reply. I'll check with them. Regards Ciro On Fri, Dec 21, 2012 at 9:09 PM, R. David Murray rep...@bugs.python.orgwrote: R. David Murray added the comment: Given the error message, my guess would be that there is a bug in the

[issue16749] Fatal Python Error

2012-12-21 Thread Leonardo DaVinci
Leonardo DaVinci added the comment: Hi David, I keep trying to unsuccessfully. Here's the problem details Problem signature: Problem Event Name: APPCRASH Application Name: python.exe Application Version: 0.0.0.0 Application Timestamp: 4f84a6c8 Fault Module Name: python27.dll