It looks like there's some trouble on the linuxsampler-lv2 (re)instantiation code, or at least it doesn't like to get re-instantiated so quickly in succession.
May I ask on how you're inserting the plugin? Is it from the track's mixer strip after you already have added a track or is it while you're at a new track dialog, that is, the track isn't inserted yet but you're adding the lv2 plugin already. I suspect trouble is on this latter case. Try adding the plugin after you add the track, please, and see whether things are any different.
Re. gdb, if you're building with debug information (./configure --enable-debug), some crash stack-tracing code is being included by default which calls gdb directly behind the scenes when a segfault occurs and a clash is certainly due if qtractor is already under gdb control. I won't be surprised if that's what you're experiencing ;)
It looks like there's some trouble on the linuxsampler-lv2 (re)instantiation code, or at least it doesn't like to get re-instantiated so quickly in succession.
May I ask on how you're inserting the plugin? Is it from the track's mixer strip after you already have added a track or is it while you're at a new track dialog, that is, the track isn't inserted yet but you're adding the lv2 plugin already. I suspect trouble is on this latter case. Try adding the plugin after you add the track, please, and see whether things are any different.
Re. gdb, if you're building with debug information (
./configure --enable-debug), some crash stack-tracing code is being included by default which callsgdbdirectly behind the scenes when a segfault occurs and a clash is certainly due if qtractor is already under gdb control. I won't be surprised if that's what you're experiencing ;)Cheers