pycharm 2.5 unable to start debug: pthread_cond_wait: Invalid argument
hello all,
since few days, i cannot start any debug with pycharm because the console displays repeatdly:
pthread_cond_wait: Invalid argument
pthread_cond_wait: Invalid argument
pthread_cond_wait: Invalid argument
i'm on MacOSX 10.6.8, and the debug worked in the past with older releases (even with the 2.5 one).
Anybody has encountered the problem?
thanks in advance,
gerard
Please sign in to leave a comment.
i forgot to say that after trying to launch debug, a python process was running on the machine and consumes 100%
Sampling process 10760 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling python (pid 10760) every 1 millisecond
Call graph:
2504 Thread_45146: Main Thread DispatchQueue_<multiple>
2504 thread_start
2504 _pthread_start
2504 initthread
2504 PyEval_CallObjectWithKeywords
2504 PyObject_Call
2504 _PyInstance_Lookup
2504 PyObject_Call
2504 PyClass_New
2504 PyObject_Call
2504 PyClassMethod_New
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyObject_Call
2504 PyClassMethod_New
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 _PyBuiltin_Init
2504 PyImport_ImportModuleLevel
2504 initimp
2504 PyThread_release_lock
2504 pthread_mutex_lock
2504 semaphore_wait_trap
2504 Thread_45148
2504 thread_start
2504 _pthread_start
2504 initthread
2504 PyEval_CallObjectWithKeywords
2504 PyObject_Call
2504 PyClass_New
2504 PyObject_Call
2504 PyClassMethod_New
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 initthread
2504 PyThread_acquire_lock
2504 _pthread_cond_wait
2504 __semwait_signal
2504 Thread_45149
2504 thread_start
2504 _pthread_start
2504 initthread
2504 PyEval_CallObjectWithKeywords
2504 PyObject_Call
2504 PyClass_New
2504 PyObject_Call
2504 PyClassMethod_New
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 PyObject_Call
2504 PyInstance_New
2504 PyEval_CallObjectWithKeywords
2504 PyObject_Call
2504 PyClass_New
2504 PyObject_Call
2504 PyClassMethod_New
2504 PyEval_EvalCodeEx
2504 PyEval_EvalFrameEx
2504 PyEval_EvalFrameEx
2504 _PyBuiltin_Init
2504 PyImport_ImportModuleLevel
2504 initimp
2504 PyThread_acquire_lock
2504 _pthread_cond_wait
2504 __spin_lock
Total number in stack (recursive counted multiple, when >=5):
22 PyEval_EvalFrameEx
11 PyEval_EvalCodeEx
11 PyObject_Call
5 PyClassMethod_New
Sort by top of stack, same collapsed (when >= 5):
__semwait_signal 2504
__spin_lock 2504
semaphore_wait_trap 2504
Sample analysis of process 10760 written to file /dev/stdout
I am facing this issue with 5.03. This happens only when we try and attach to a already running process. It does not happen when we start the script in pycharm.