[Jack-Devel] libjack.so and libjackserver.so bug
falktx at gmail.com
Tue Mar 6 10:14:46 CET 2018
This is a known scenario.
Those 2 libs share some code, but in a different way.
A client application is never supposed to control the server.
Do not link against the 2 libraries from within the same application,
and you'll be fine.
On 06.03.2018 09:04, Christoph Kuhr wrote:
> Hi *,
> I observed some strange behavior of libjack and libjackserver.
> If I have a multiprocessing application with one jack server fork and
> one jack client fork, jack_client_open crashs.
> Here the backtrace:
> #0 __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:174
> #1 0x00007f83dddb803f in jack_find_driver_descriptor(_JSList*, char
> const*) () from /usr/local/lib/libjackserver.so.0
> #2 0x00007f83dddb9ef8 in Jack::JackServerGlobals::Init() () from
> #3 0x00007f83dddb64f8 in jack_client_open_aux(char const*,
> JackOptions, JackStatus*, __va_list_tag*) () from
> #4 0x00007f83dddb67b1 in jack_client_open () from
> #5 0x0000000000414f04 in talker_Process (arguments=0x63f680
> <arguments>) at ../src/net/avb/talker/talker_process.c:395
> #6 0x000000000042d487 in avbruntime (arguments=0x63f680 <arguments>)
> at ../src/avbruntime.c:644
> #7 0x000000000042e888 in main (argc=11, argv=0x7ffebee6f678) at
> The interesting thing is, jack_client_open keeps crashing if I remove
> all the jack server code.
> It was neccessary to remove the -ljackserver linker option as well,
> because the client code linked against libjackserver.so instead of
> This means it is not possible to have a jack server and a jack client
> in a single multiprocessing application.
> Jack-Devel mailing list
> Jack-Devel at lists.jackaudio.org
More information about the Jackaudio