[alsa-devel] Atomic operations not multi-thread aware
Hi, please take a a look at gsequencer.org especially at:
libags-audio * http://gsequencer.org/api/ags/ags-AgsPort.html
gsequencer * http://gsequencer.org/api/ags/ags-AgsLineMember.html
I can crash my application while modifying values of the LADSPA plugin assigned dial widget what uses atomic operations and a task engine ...
Where can me read about state of Atomic Operations of linux or glibc? Me doing further investigation.
bests Joël
Hi, further informations:
http://linuxfromscratch.org http://minos-one.org/downloads/minos-one_v1.3.iso - WARNING includes bash bug! Note for best stability you have to dd the live DVD to hard-disk drive.
linux kernel 3.14.25-rt22 gcc (GCC) 4.9.2
bests Joël
On Sun, Mar 29, 2015 at 2:52 PM, Joël Krähemann weedlight@gmail.com wrote:
Hi, please take a a look at gsequencer.org especially at:
libags-audio
gsequencer
I can crash my application while modifying values of the LADSPA plugin assigned dial widget what uses atomic operations and a task engine ...
Where can me read about state of Atomic Operations of linux or glibc? Me doing further investigation.
bests Joël
Joël Krähemann wrote:
I can crash my application while modifying values of the LADSPA plugin assigned dial widget what uses atomic operations and a task engine ...
Atomic operations are thread-safe by definition.
However, plugin functions might not be. The LADSPA spec does not say anything about it, so I guess you have to serialize all accesses.
And what does this have to do with ALSA?
Regards, Clemens
participants (2)
-
Clemens Ladisch -
Joël Krähemann