Subject: Re: [ecasound] major race condition in ECI
From: Eric Dantan Rzewnicki (eric_AT_zhevny.com)
Date: Tue Sep 28 2004 - 03:56:59 EEST
Jesse Chappell wrote:
> Hey Kai, it's been a while..... I'm sending this to the list,
> but I don't think I'm added to it yet, hence the CCs.
> There was a problem that plagued me years ago, and still does today, so
> I dove in to debug it. Basically, using the ECI interface through
> python was often causing read/sync errors in the ecasoundc_sa
> subsystem when issuing the 'start' command. I turned on debugging
> in ecasound_sa.c and lo and behold, found the problematic behavior:
> --- cut --------
> (ecasoundc_sa) writing command 'start' (cmd-counter=13).
> (ecasoundc_sa) clearing list, i=(nil)
> (ecasoundc_sa) found content, loglevel=2, msgsize=36.
> (ecasoundc_sa) found content, loglevel=2, msgsize=36.
> (ecasoundc_sa) found content, loglevel=2, msgsize=36.
> (ecasoundc_sa) found content, loglevel=2, msgsize=36.
> (ecasoundc_sa) gen-content validated: <<< (eca-engine) Prefi2ll5i6n g0 i-/ >>>
> (ecasoundc_sa) timeout when reading return values (attempts=1)!
I've had a problem with my python eci scripts, too. But, I thought I was
just doing something dumb since I'm pretty new to programming. I have a
lot of print statements in my python scripts to get last strings and
last floats and such. When I run a script from the commandline I only
see each line of output once. But, when I started running them from cron
with standard out redirected to a file for logging purposes I got many
instances of each line written to the file and many of them out of
order. Later I realized this before was only related to the redirection
and had nothing to do with cron.
Could this be another symptom of the same race condition between threads?
A copy of the script and a sample logfile from a stdout redirected run
are attached.
Thanks Kai and thank you, too, Jesse.
-Eric Rz.
This archive was generated by hypermail 2b28 : Tue Sep 28 2004 - 03:57:27 EEST