padsp: Handle eol in info callbacks correctly

When receiving an eol, the object will be NULL and we're not handling
this correctly. Thanks to Drew Ogle <dantealiegri@gmail.com> for
reporting this and providing a patch.
This commit is contained in:
Arun Raghavan 2011-07-11 20:59:30 -07:00
parent f69cbdbdf7
commit 157bc4ef3b

View file

@ -1222,7 +1222,7 @@ fail:
static void sink_info_cb(pa_context *context, const pa_sink_info *si, int eol, void *userdata) { static void sink_info_cb(pa_context *context, const pa_sink_info *si, int eol, void *userdata) {
fd_info *i = userdata; fd_info *i = userdata;
if (!si || eol < 0) { if (eol < 0) {
i->operation_success = 0; i->operation_success = 0;
pa_threaded_mainloop_signal(i->mainloop, 0); pa_threaded_mainloop_signal(i->mainloop, 0);
return; return;
@ -1244,7 +1244,7 @@ static void sink_info_cb(pa_context *context, const pa_sink_info *si, int eol, v
static void source_info_cb(pa_context *context, const pa_source_info *si, int eol, void *userdata) { static void source_info_cb(pa_context *context, const pa_source_info *si, int eol, void *userdata) {
fd_info *i = userdata; fd_info *i = userdata;
if (!si || eol < 0) { if (eol < 0) {
i->operation_success = 0; i->operation_success = 0;
pa_threaded_mainloop_signal(i->mainloop, 0); pa_threaded_mainloop_signal(i->mainloop, 0);
return; return;