[ecasound] orphaned controller

From: Adam Linson <adam@email-addr-hidden-s.com>
Date: Sun Nov 20 2005 - 16:05:00 EET


I am running ecasound-2.4.4-cvs-20051021 and just noticed a new and
possibly unintended behavior which seems to have been recently

Basically, if (under interactive mode or with an api) I add a cop with
two controllers (ctrl) and then remove the cop, one of the controllers
is orphaned. I am somewhat certain that previously, when a cop was
removed, all it's attached controllers were removed along with it.
That fact that only one controller now remains instead of neither or
both leads me to think this is an unintended behavior.

Once the controller is orphaned, ecasound continues to run if no
further command is issued. Depending on what command is issued next,
however, there is typically an uncontrolled exiting of the program
(sometimes a segfault, sometimes a broken pipe, and sometimes an
apparently clean but unannounced exit).

Now that I think about it, I have only tested this with 2x -km, not
sure if the same thing happens with other controllers.

I would be happy to provide more details as needed.


This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op ick
Ecasound-list mailing list
Received on Mon Nov 21 12:15:09 2005

This archive was generated by hypermail 2.1.8 : Mon Nov 21 2005 - 12:15:09 EET