[Ardour-Users] Ardour 2 + Ubuntu segfault
hakan at koseoglu.org
Thu Sep 29 03:19:42 PDT 2011
I have an interesting problem here.
I have an (slightly) modified Kubuntu laptop (64 bit, 11.04) where
ardour2 segfaults immediately at startup. Funnily enough I thought I had
the same problem on an other Kubuntu laptop here (which is a lot less
modified with no extra PPAs), well that was crashing as well but with a
different issue which was resolved after uninstalling
It looks like it doesn't like something in the lv2 stack but I haven't
managed to figure out yet!
Any help or suggestions are much appreciated.
[ 8581.989666] ardour-2.8.11: segfault at 8 ip 00007fadf6869730
sp 00007fff78248030 error 4 in libslv2.so.9.2.0[7fadf6861000+c000]
I ran it through valgrind and here's the bit where it falls over:
==16577== Process terminating with default action of signal 11 (SIGSEGV)
==16577== Access not within mapped region at address 0x8
==16577== at 0xD44E730: slv2_value_new (in /usr/lib/libslv2.so.9.2.0)
==16577== by 0xD44EEF0: slv2_world_load_directory (in
==16577== by 0xD44EFB3: slv2_world_load_path (in
==16577== by 0xD44F1C9: slv2_world_load_all (in
G==16577== by 0x5083B73: ARDOUR::LV2World::LV2World() (lv2_plugin.cc:563)
==16577== by 0x4FCE30A: ARDOUR::PluginManager::PluginManager()
==16577== by 0x4F78731: ARDOUR::init(bool, bool) (globals.cc:358)
==16577== by 0x52BAD1: ARDOUR_UI::ARDOUR_UI(int*, char***)
==16577== by 0x75B7DE: main (main.cc:392)
==16577== If you believe this happened as a result of a stack
==16577== overflow in your program's main thread (unlikely but
==16577== possible), you can try to increase the size of the
==16577== main thread stack using the --main-stacksize= flag.
==16577== The main thread stack size used in this run was 8388608.
Hakan (m1fcj) - http://www.hititgunesi.org
"What part of 'ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn'
don't you understand?"
More information about the Ardour-Users