Re: [ecasound] Ecasound build process stuck after tests

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Thu Mar 31 2011 - 00:04:47 EEST


On Wed, 30 Mar 2011, Alessandro Ghedini wrote:

> I have done some tests (running stresstest.rb alone many times) and the
> problem is indeed, in stresstest.rb. I found out that it get stuck on
> (AFAICS) a random basis (quite rarely though). When it happens and I
> interrupt the process (with Ctrl+C) I get:
> ./ecasound.rb:93:in ``': Interrupt
> from ./ecasound.rb:93
> from stresstest.rb:19:in `require'
> from stresstest.rb:19
> Since I am not that familiar with Ruby, I don't know if there is any
> technique to get some additional info, but that output is not (to me) much
> helpful. Any idea?

I'll cc this directly to Jan as well (this is he's code originally).

I'm a ruby newbie myself, but browsing the code this seems to fail at the
first instance when stresstest.rb needs to run the just compiled ecasound
binary (from ../ecasound/ecasound).

The code should handle all the common cases (invalid string returned, no
executable bit set, file not found), but I suspect something less common
happens that causes this check to fail.

I could generate a similar error by doing:
sh> rm ../ecasound/ecasound
sh> mkfifo ../ecasound/ecasound
sh> chmod +x ../ecasound/ecasound
sh> ./stresstest.rb

The error message is identical, so I think I'm on to something. Please
check what the ecasound binary really is (when you can reproduce the
issue). Is the file the actual binary, or perhaps some linker script or
other build process intermediaery?

Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website.
Ecasound-list mailing list
Received on Thu Mar 31 00:15:04 2011

This archive was generated by hypermail 2.1.8 : Thu Mar 31 2011 - 00:15:04 EEST