bap: Fix use of unintialized variable This fixes the following trace found with valgrind: Syscall param socketcall.setsockopt(optval) points to uninitialised byte(s) at 0x5318B0E: setsockopt (in /usr/lib64/libc.so.6) by 0x39C454: iso_set_qos (btio.c:899) by 0x39C622: bt_io_set (btio.c:1900) by 0x37F3B3: iso_do_big_sync (bap.c:2874) by 0x3991EC: server_cb (btio.c:265) by 0x3991EC: server_cb (btio.c:242) by 0x496C4FB: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.7600.6) by 0x49CA6B7: ??? (in /usr/lib64/libglib-2.0.so.0.7600.6) by 0x496BAFE: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.7600.6) by 0x4F9694: mainloop_run (mainloop-glib.c:66) by 0x4F9B27: mainloop_run_with_signal (mainloop-notify.c:188) by 0x2BE8F2: main (main.c:1464) Address 0x1fff0004c1 is on thread 1's stack in frame #2, created by bt_io_set (btio.c:1870)

Diffstat

1 files changed, 1 insertions(+), 0 deletions(-)