Arch Linux

Stack trace:

Thread 1 (Thread 0x7fe389bdd700 (LWP 2853)):
#0 0x0000000000000000 in ?? ()
#1 0x00000000004bca4b in jack_open_audio ()
#2 0x000000000046b39e in sys_reopen_audio ()
#3 0x000000000046b9cd in glob_audio_setapi ()
#4 0x000000000045452c in pd_typedmess ()
#5 0x000000000045c855 in binbuf_eval ()
#6 0x0000000000463ca4 in socketreceiver_read ()
#7 0x0000000000463125 in ?? ()
#8 0x0000000000460058 in m_mainloop ()
#9 0x00007fe388811790 in __libc_start_main () from /usr/lib/libc.so.6
#10 0x0000000000411a39 in _start ()

As Allan suggests on the board [1], this can be omitted by adding options=(!buildflags). At least in my case, I can confirm that.

[1] https://bbs.archlinux.org/viewtopic.php?pid=1562421#p1562421

It crashes when using "jack2" or "jack2-dbus", but not when using old "jack".

I have the same problem with jack2 running. I tried installing jack but that didn't help, then I installed linux-rt to see if that helped. both did not work and Pd still crashes when I try enabling jack.

Same here:

pd -jack -d 1
set pd_whichmidiapi 0
pdtk_watchdog
set ::tmp_path {}
set ::sys_searchpath $::tmp_path
set ::tmp_path {}
lappend ::tmp_path {/home/antanas/pd-externals}
lappend ::tmp_path {/usr/local/lib/pd-externals}
lappend ::tmp_path {/usr/lib/pd/extra}
set ::sys_staticpath $::tmp_path
set ::startup_flags {}
set ::startup_libraries {}
pdtk_pd_startup 0 46 7 {} { {OSS 2} {ALSA 1} {jack 5} } { {OSS-MIDI 0} {ALSA-MIDI 1} } {DejaVu Sans Mono} bold
set pd_whichapi 5
set pd_whichmidiapi 0
Segmentation fault (core dumped)

@speps: Can you please apply the fix?
pd is quite useless in a real-time audio/ pro-audio context in this state.

I can also confirm, that the package works, when build with options=('!strip' '!buildflags')

There's also an upstream bug report, but they don't know about it working here, when using options=(!buildflags) (yet): https://sourceforge.net/p/pure-data/bugs/1228/

@speps: It seems the global hardening flags are causing the trouble with pd and jack2.
So there are two options: Adding !buildflags to options or adding the global buildflags during build while ommitting CPPFLAGS="-D_FORTIFY_SOURCE=2"

Is there anything that can be done to get this bug fixed at last? I can also confirm that adding !buildflags to options resolve the issue with using jack.

@jmx: You could use pd-git from the AUR (https://aur.archlinux.org/packages/pd-git/).
Just added it with !buildflags.

I'm not sure pd will be fixed in time and might even be dropped to AUR, because of lack of maintenance (which I hope it won't).

The linker flag -Wl,--as-needed results in /usr/bin/pd omitting the link to libjack.so.
Since libjack has its functions marked as weak symbols, gcc does not signal an undefined symbol error at link time. However the jack functions receive null addresses at runtime, producing a jump to adress 0 and subsequent crash, as it can be seen in valgrind.
I am not quite sure why --as-needed would remove jack from the link though.

I think this doesn't apply to pd > 0.48 anymore, so this can probably be closed.