[ardour-dev] 2.0.2 issues...

Lawrence T. Levine levine at yellowchicken.com
Sat May 12 05:43:15 PDT 2007

>> 4) if I start jackd manually it starts fine however... when I start
>> ardour2.0.2 it segfaults after loading the bindings.
> Do you mean jackd segfaults, or ardour2 segfaults?
> Error messages would be helpful here, as would details of your
> hardware and operating system.

Jack keeps running fine.  Ardour2 segfaults right after it says it's 
loaded the bindings.

when I run ardour2 dmesg consistetly reports the following at the time of 
segfault:  ardour-2.0.2[6676]: segfault at 0000000000000005 rip 
ffffffffff600119 rsp 0000000040173c40 error 6

btw - if it helps, when qjack segfaults it reports:
qjackctl[6382]: segfault at 0000000000000005 rip ffffffffff600119 rsp 
000000004007dc40 error 6

I'm running:

Linux version 2.6.20-rt8 (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) 

AMD64 - bunch of ram...

As I stated originally beta12 was running great (0 xruns and <5 latency). 

Thanks for any insights.  Since I believe this has 'something' to do with 
jack maybe I should remove jack and recompile/reinstall it.  Maybe I 
borked something in it.  Although, it doesn't crash.


More information about the Ardour-Dev mailing list