Re: Bug report: segfault, etd: JACK support is to blame?

On Thu, May 10, 2012 at 03:45:25PM -0400, 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:
> #0  0x0000000000566822 in SAMPLE_ITERATOR_CHANNEL::begin (this=0x7fffd8f60358,
>     channel=0) at samplebuffer_iterators.cpp:68
> #1  0x0000000000519f0c in EFFECT_DELAY::process (this=0x7fffd8f60330)
>     at audiofx_timebased.cpp:209
> #2  0x00000000004bebde in CHAIN::process (this=0x7fffd8002e30)
>     at eca-chain.cpp:825
> #3  0x000000000056082c in ECA_ENGINE::process_chains (this=0x7fffd8012c80)
>     at eca-engine.cpp:1699
> #4  0x00000000005653c2 in ECA_ENGINE::engine_iteration (this=0x7fffd8012c80)
>     at eca-engine.cpp:688
> #5  0x000000000053a5c4 in eca_jack_process_engine_iteration (nframes=128,
>     arg=0x7fffd800cc40) at audioio_jack_manager.cpp:457
> #6  0x000000000053b609 in eca_jack_process_timebase_slave (arg=0x7fffd800cc40,
>     nframes=128) at audioio_jack_manager.cpp:565
> #7  eca_jack_process_callback (arg=0x7fffd800cc40, nframes=128)
>     at audioio_jack_manager.cpp:403
> #8  eca_jack_process_callback (nframes=128, arg=0x7fffd800cc40)
>     at audioio_jack_manager.cpp:362
This trace caused me to go back and try the same operations without
JACK (only alsa). This bug simply does *not* occur without the JACK
factor. I repeated the test several times. 

Cheers,
S.M.

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecasound-list