well, i've just built linuxsampler from svn trunk rev.2322 today and it breaks on me too.
it all seems related to the lv2/lilv state api feature recently introduced in the linuxsampler-lv2 plugin implementation.
if you build qtractor with ./configure --enable-debug you'll get a better stacktrace which always points you to linuxsampler's PluginLv2::Restore at the segfault crash spot.
previously, the lv2 state feature extension (when is was independent from a lilv api) it was working great--blame this to the all-mighty-l33t aka. drobilla xD
i'll have to investigate this too, probably i'll have to take measures on this kind of hidenbugs o.O
[UPDATE:] fixed on svn trunk rev.2743+ (aka. qtractor 0.5.3.38+) -- in fact it is a bug in linuxsampler lv2 state interface, due to lack of validation for some null input parameter.
well, i've just built linuxsampler from svn trunk rev.2322 today and it breaks on me too.
it all seems related to the lv2/lilv state api feature recently introduced in the linuxsampler-lv2 plugin implementation.
if you build qtractor with
./configure --enable-debugyou'll get a better stacktrace which always points you to linuxsampler'sPluginLv2::Restoreat the segfault crash spot.previously, the lv2 state feature extension (when is was independent from a lilv api) it was working great--blame this to the all-mighty-l33t aka. drobilla xD
i'll have to investigate this too, probably i'll have to take measures on this kind of hidenbugs o.O
[UPDATE:] fixed on svn trunk rev.2743+ (aka. qtractor 0.5.3.38+) -- in fact it is a bug in linuxsampler lv2 state interface, due to lack of validation for some null input parameter.
cheers