[PD] status of leap motion controller in Pd, especially on Linux?

[Max]

I think you need to start pd with the leap library preloaded:

LD_PRELOAD=~/path/to/LeapDeveloperKit/LeapSDK/lib/x64/libLeap.so 
~/path/to/pd/bin/pd ~/path/to/patch.pd




On 12.03.19 14:30, Peter P. wrote:
> * Peter P. <peterparker at fastmail.com> [2019-03-11 23:03]:
>> So it seems that there is an OS X binary of [leapmotion] at
>> http://puredatajapan.info/?page_id=1514
>> of which I assume it was compiled with the v1 SDK
>>
>> as well as a 64bit linux binary at
>> https://philtgun.me/2017/02/04/leap-synthesizer-in-pure-data/
>> which I assume to be v1 SDK as well.
> 
> I tried this linux binary external today with an actual leap motion
> controller and the leapd starts fine, LeapControlPanel works as well,
> but Pd crashes once I ask the successfully loaded [leapmotion] external
> for data with a single or continuous bangs.
> 
> Here is the backtrace of it. I hope anyone can give me a hint about what I could try next?
> thanks! P
> 
> ------------------------------
> 
> (gdb) run
> Starting program: /usr/bin/pd -path linux64bit Pd_leapmotion_0.1_mac/leap_motion_help.pd
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [Detaching after fork from child process 14993]
> [Detaching after fork from child process 14996]
> [New Thread 0x7ffff6d7c700 (LWP 15011)]
> [New Thread 0x7ffff657b700 (LWP 15012)]
> [New Thread 0x7ffff5d7a700 (LWP 15013)]
> [New Thread 0x7fffeffff700 (LWP 15014)]
> [New Thread 0x7ffff5579700 (LWP 15015)]
> [New Thread 0x7ffff4d78700 (LWP 15016)]
> [New Thread 0x7fffef7fe700 (LWP 15017)]
> [New Thread 0x7fffee7fc700 (LWP 15022)]
> [New Thread 0x7fffeeffd700 (LWP 15021)]
> [New Thread 0x7fffed7fa700 (LWP 15026)]
> [New Thread 0x7fffedffb700 (LWP 15023)]
> 
> Thread 1 "pd" received signal SIGILL, Illegal instruction.
> 0x00007ffff6d8cca4 in ?? () from linux64bit/leapmotion.pd_linux
> (gdb) watchdog: signaling pd...
> (gdb) btwatchdog: signaling pd...
> watchdog: signaling pd...
> 
> #0  0x00007ffff6d8cca4 in ?? () from linux64bit/leapmotion.pd_linux
> #1  0x00007ffff6d8d139 in ?? () from linux64bit/leapmotion.pd_linux
> #2  0x00007ffff6d964c6 in flext_base_single::TryMethTag(flext_base_single::Item*, _symbol const*, int, _atom const*)
>      () from linux64bit/leapmotion.pd_linux
> #3  0x00007ffff6d966b8 in flext_base_single::FindMeth(int, _symbol const*, int, _atom const*) ()
>     from linux64bit/leapmotion.pd_linux
> #4  0x00007ffff6d9688c in flext_base_single::CbMethodHandler(int, _symbol const*, int, _atom const*) ()
>     from linux64bit/leapmotion.pd_linux
> #5  0x000055555560e611 in outlet_bang ()
> #6  0x00005555555a543e in ?? ()
> #7  0x00005555555beb81 in ?? ()
> #8  0x000055555560bc99 in pd_typedmess ()
> #9  0x0000555555608637 in binbuf_eval ()
> #10 0x00005555556199d6 in socketreceiver_read ()
> #11 0x0000555555618aec in ?? ()
> #12 0x0000555555611cf2 in m_mainloop ()
> #13 0x00007ffff733509b in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
> #14 0x000055555556b22a in _start ()
> (gdb) watchdog: signaling pd...
> Quit
> (gdb) watchdog: signaling pd...
> Quit
> (gdb) quiwatchdog: signaling pd...
> t
> A debugging session is active.
> 
>          Inferior 1 [process 14989] will be killed.
> 
> Quit anyway? (y or n) y
> 
> 
> 
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>