Hi,
On Thu, 10 May 2012, S. Massy wrote:
> It seems, however, that aadding many such ops in a short period of time
> causes ecasound to segfault. Here is the backtrace:
this looks a lot like something that could happen without the recent fix
in git master (commit ca925a389154774ca7ff69d2f141f1c9000a2050 I pushed on
Apr 17). Are you running the latest git?
The problem itself looks clear;
[OBJECTS ] (eca-control) processing cmd and arg: cop-add -etd:602.666666666667,0,1,100,100 <9087>
[SYSTEM ] (eca-engine) wait_for_editlock <9088>
[SYSTEM ] (eca-engine) Signaling editlock <9089>
[SYSTEM ] (eca-engine) wait_for_editlock complete, ret -1 <9090>
.. that's not right, there should be a "Signaling stop" message there. But
in your log, this does not happen and the -etd chainop gets added while
engine is processing, and this will cause a crash. This also matches with
the DBC_CHECK failure you posted in your later post.
But the problem is that this should be fixed in git already and the code
looks correct. It could be some case is still missed, even with the latest
code...
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Received on Sun May 20 00:15:02 2012
This archive was generated by hypermail 2.1.8 : Sun May 20 2012 - 00:15:02 EEST