[ecasound] Bug with "direct" handling (nodb)

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: [ecasound] Bug with "direct" handling (nodb)
From: S. Massy (theanaloguekid_AT_tak.net.dhis.org)
Date: Sat Oct 06 2001 - 16:56:01 EEST

Hmm, there seems to be a bug when not using the proxy objects, for example
issuing:
$ ecasound -d:255 -B:nonrt -i:/root/test.wav -o:/dev/dsp
ecasound will process the file correctly but will segfault upon exit;
looking through the debug info, I see:
----------
...
(eca-chainsetup) Deleting chain "default".
CHAIN destructor!
(eca-chainsetup) Deleting audio object "/root/test.wav".
(file-io) Closing file /root/test.wav
(eca-chainsetup) Deleting audio object "/dev/dsp".
(eca-chainsetup) Deleting garbage audio object "/root/test.wav".
Segmentation fault
----------

My guess is that ecasound is trying to close an object that has already been
dealt with, tries to access something that is no longer there and triggers a
segfault... 

--
To unsubscribe send message 'unsubscribe' in the body of the
message to <ecasound-list-request_AT_wakkanet.fi>.

New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Sat Oct 06 2001 - 16:51:35 EEST