<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - PulseAudio Python Binding PyEval_CallFunction segfault in pa_mainloop_dispatch based on pa_threaded_mainloop" href="https://bugs.freedesktop.org/show_bug.cgi?id=61328#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - PulseAudio Python Binding PyEval_CallFunction segfault in pa_mainloop_dispatch based on pa_threaded_mainloop" href="https://bugs.freedesktop.org/show_bug.cgi?id=61328">bug 61328</a> from <a class="email" href="mailto:xiangzhai83@gmail.com" title="Xiang Zhai <xiangzhai83@gmail.com>"> Xiang Zhai</a> <pre>Thank Tanu`s reply :) Yes pa_threaded_mainloop is working correctly in my cgtk.c and console.py testcases <a href="https://github.com/xiangzhai/pypulseaudio/blob/master/examples/cgtk.c">https://github.com/xiangzhai/pypulseaudio/blob/master/examples/cgtk.c</a> But the pygtk.py testcase is different from console.py, because there is already a GMainLoop in PyGtk (Gtk+-2.0 Python Binding), so is it possible that shared data from concurrent modifications by pa_threaded_mainloop && GMainLoop? PyEval_CallFunction is Python C API, it acts like call function pointer, such like PyEval_CallFunction(py_callback, argv, ...) PyGILState_Release is another Python C API, it acts like pthread_mutex_unlock, or pa_threaded_mainloop_unlock. Anyway thanks a lot for your reply :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>