brainflow: Start straming and then Segmentation fault error
Dear Andrey, I just found BrainFlow on GitHub and I think it is fantastic. I run into problems: it crashes when it starts streaming.
I am a python user, Ubuntu 18.04, Python 3.8, Ganglion board with USB dongle BLED112. brainflow==2.1.0 I am running the script from the code samples: https://brainflow.readthedocs.io/en/stable/Examples.html#python-get-data-from-a-board
python main.py --board-id 1 --serial-port /dev/ttyACM0 --mac-address e0:06:15:36:28:44 --log
[2019-12-22 19:29:33.146] [brainflow_logger] [info] incomming json: {
"ip_address": "",
"ip_port": 0,
"ip_protocol": 0,
"mac_address": "e0:06:15:36:28:44",
"other_info": "",
"serial_port": "/dev/ttyACM0"
}
[2019-12-22 19:29:33.146] [brainflow_logger] [debug] ganglionlib initialized
[2019-12-22 19:29:33.146] [brainflow_logger] [info] search for e0:06:15:36:28:44
[2019-12-22 19:29:35.117] [brainflow_logger] [debug] use stub streamer
[2019-12-22 19:29:35.340] [brainflow_logger] [debug] start streaming
Segmentation fault (core dumped)
From: https://stackoverflow.com/questions/13654449/error-segmentation-fault-core-dumped
“Segmentation fault (core dumped)” is the string that Linux prints when a program exits with a SIGSEGV signal and you have core creation enabled. This means some program has crashed. As you are getting this error from running Python, this means the Python interpreter has crashed. There are only a few reasons this can happen:
- You’re using a third-party extension module written in C, and that extension module has crashed.
- You’re (directly or indirectly) using the built-in module ctypes, and calling external code that crashes.
- There’s something wrong with your Python installation.
- You’ve discovered a bug in Python that you should report.
I suppose we are in the first case. Thanks in advice for your effort and time.
I wish you lovely holidays and a happy new year. Kind Regards Matteo Mazzanti
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 27 (13 by maintainers)
We’ve fixed it. It was a bug inside vendor’s library which we use to communicate with BLE device. Version 2.1.2 should work
Thanks! We also managed to repr it on Ubuntu and debugging right now