Re: Segfault using zita-j2a

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 25.10.2012 17:51, schrieb Fons Adriaensen:
> On Thu, Oct 25, 2012 at 05:23:28PM +0200, Robin Gareus wrote:
> 
>> Classic race condition. The jack_client is activated before the
>> resampler is initialized.
>>
>> zita-j2a.cc:200 creates the jack-client and calls jack_activate.
>> process_callbacks can arrive starting now.
>>
>> but not until zita-j2a.cc:211 calls J->start() the data-structures
>> required to do the processing are initialized.
>>
>> Easiest solution is probably to check if start() has been called in the
>> process callback:
> 
> The code to do that is already present: jackclient:cc line 311.
> There must be some other problem.

valgrind's output is here: http://dpaste.com/hold/818241/

when running in the debugger, one can see the input buffer full of 0x00s
(as floats). Should be okay since we are not connected via JACK to anything.

	Jannis

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user


[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux