JackOfAll wrote: > I tried to run a quick test on the WB with "-u". Got no output, so tried > running it on my desktop from Eclipse debugger. Looks like a deadlock/ > resource problem on the output buffer mutex. > > Thread 1: slimproto_run() at slimproto.c:531 LOCK_O (wants and is > waiting for LOCK) > > Thread 3: output_thread() at output.c:662 LOCK (wants and is waiting for > LOCK) > > Thread 4: _write_samples() at process.c has the lock having called > LOCK_O before going into while(frames > 0) > frames_t f = min(_buf_space(outputbuf), _buf_cont_write(outputbuf)) / > BYTES_PER_FRAME; >
Thats interesting.... I was intending it never to get to the point where the output buffer was completely full. This seems reasonable way to trap, but let me look at again tomorrow. ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=98544 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
