[pulseaudio-tickets] [Bug 61328] PulseAudio Python Binding PyEval_CallFunction segfault in pa_mainloop_dispatch based on pa_threaded_mainloop

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=61328

--- Comment #3 from Xiang Zhai <xiangzhai83 at gmail.com> ---
Thank Tanu`s reply :)

Yes pa_threaded_mainloop is working correctly in my cgtk.c and console.py
testcases https://github.com/xiangzhai/pypulseaudio/blob/master/examples/cgtk.c

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 :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20130223/cec6a8a6/attachment.html>