Re: BEAST "contitous integration" packages fail to start

On 05.11.2015 15:17, Stefan Westerfeld wrote:

I've tried to use the new "continous integration" packages: I added

deb vivid main

to /etc/apt/sources.list (on kubuntu vivid), and installed beast using

$ aptitude install beast libbse-dev

finally, starting beast results in a crash, so here is the gdb stacktrace.

$ gdb --args beast
GNU gdb (Ubuntu 7.9-1ubuntu1) 7.9
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from beast...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/beast 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/".
process 960 is executing new program: /usr/bin/beast-0.9.3
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/".
[New Thread 0x7fa42855d700 (LWP 967)]
[New Thread 0x7fa41ffff700 (LWP 969)]
[New Thread 0x7fa4274e4700 (LWP 968)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa42855d700 (LWP 967)]
0x00007fa43301a12b in bse_categories_register () from /usr/lib/x86_64-linux-gnu/
(gdb) bt
#0  0x00007fa43301a12b in bse_categories_register () at /usr/lib/x86_64-linux-gnu/
#1  0x00007fa43303c497 in bse_ladspa_plugin_check_load () at /usr/lib/x86_64-linux-gnu/
#2  0x00007fa433074afe in  () at /usr/lib/x86_64-linux-gnu/
#3  0x00007fa43193ab4d in g_main_context_dispatch (context=0x7fa420001600) at 
#4  0x00007fa43193ab4d in g_main_context_dispatch (context=context entry=0x7fa420001600) at 
#5  0x00007fa43193af20 in g_main_context_iterate (context=context entry=0x7fa420001600, block=block 
entry=1, dispatch=dispatch entry=1, self=<optimized out>) at 
#6  0x00007fa43193afcc in g_main_context_iteration (context=0x7fa420001600, may_block=1) at 
#7  0x00007fa4330373b4 in  () at /usr/lib/x86_64-linux-gnu/
#8  0x00007fa43169ce30 in  () at /usr/lib/x86_64-linux-gnu/
#9  0x00007fa4324e46aa in start_thread (arg=0x7fa42855d700) at pthread_create.c:333
#10 0x00007fa430e00eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

BseCategories is currently undergoing ABI changes and will eventually be replaced like all sfidl based APIs.

Since I'm not seeing the crash here, I suspect that you installed beast and libbse-dev from very recent 
master, but still have a binary plugin like specmorph around that was compiled against Beast from say 
yesterday or the day before that.
ATM, due to the migrations (described in most branch merges into master will break ABI and API, 
and the next release version number is going to reflect that of course.

For external plugins that means, those must be frequently recompiled.

   Cu... Stefan

Yours sincerely,
Tim Janik
Free software author and speaker.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]