On 10/02/10 03:13, Ivica Ico Bukvic wrote:
> Many thanks for the clarification Robin, really appreciate it!
>
> One more thing I realized, isn't the secondary thread effectively blocking
> the lock on the main thread because the mutex_lock is placed before the cond
> call or is this the right wa
-Original Message-
> From: Robin Gareus [mailto:ro...@gareus.org]
> Sent: Friday, October 01, 2010 9:01 PM
> To: Ivica Ico Bukvic
> Cc: linux-audio-dev@lists.linuxaudio.org
> Subject: Re: [LAD] question about multithreaded externals in Pd
>
> Hi Ico,
>
> just quick
Hi Ico,
just quick:
pthread_create() returns after the thread context has been created; but
the actual thread-function is not run directly.
The main function may continue before the actual thread is run.
In your case the pd_cwiid_doConnect() can be called before the
pd_cwiid_pthreadForAudioUnfr
Hi all,
I am wondering if anyone can shed some light on the following
predicament. I am by no means a multi-threading guru so any insight
would be most appreciated.
The following are relevant excerpts from the code of an external. AFAIK
the external initializes mutex and cond and spawns a seconda
