search

labstreaminglayer / liblsl-Java

Java bindings for liblsl
MIT License
5 stars 10 forks source link

Loguru SIGSEGV #3

Open SunnyJames opened 4 years ago

SunnyJames commented 4 years ago

I'm struggling to integrate liblsl-Java JNA interface with a larger open source java program for purposes of sending LSL markers for user interface interactions. The example code is very straightforward and everything works as expected in testing outside of the larger program I an integrating with. But when incorporating liblsl directly, while the native library loads and appears to begin running I get an immediate memory access violation after creating an outlet. Library and native interfaces work as expected with Python and Java outside of the project that I am working on.

I'm not particularly familiar with the nuances of JNA, so unsure if there are other options which can be passed when loading the native interface to help diagnose the issue.

Creating a new StreamInfo... Creating an outlet... date time ( uptime ) [ thread name/id ] file:line v| 2020-09-30 20:49:37.925 ( 0.085s) [main thread ] loguru.cpp:607 INFO| arguments: liblsl 2020-09-30 20:49:37.925 ( 0.085s) [main thread ] loguru.cpp:610 INFO| Current dir: /home/vagrant/testing/eclipse-workspace/EventListener 2020-09-30 20:49:37.925 ( 0.085s) [main thread ] loguru.cpp:612 INFO| stderr verbosity: 0 2020-09-30 20:49:37.925 ( 0.085s) [main thread ] loguru.cpp:613 INFO| ----------------------------------- 2020-09-30 20:49:37.925 ( 0.085s) [main thread ] common.cpp:50 INFO| git:v1.14.0b3/branch:HEAD/build:/compiler:GNU-8.3.0/link:shared

Loguru caught a signal: SIGSEGV 2020-09-30 20:49:39.056 ( 1.216s) [ E6233700] :0 FATL| Signal: SIGSEGV

tstenner commented 4 years ago

This is an issue that has popped up recently, and so far I haven't been able to reproduce it.

How reliable does the issue occur? If it's all the time, I can prepare several liblsl dlls to test against so we can pinpoint when the issue was introduced.