SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment

[dkkeller]

Description:

nrfutil and especially the pc-ble-driver-py seem to not work with virtual pyenv environments.

I am expecting it has something to do with the lib files _nrf_ble_driver_sd_api_vX.so

Environment:

• macOS (10.15.4)
• Shell: fish (2.7.1)
• pyenv (1.2.18)
• nrfutil (6.1.0)
• pc_ble_driver_py (0.14.2)
• otool -L /Users/myusername/.pyenv/versions/my3.7.6/lib/python3.7/site-packages/pc_ble_driver_py/lib/_nrf_ble_driver_sd_api_v5.so
  • /Users/myusername/.pyenv/versions/my3.7.6/lib/python3.7/site-packages/pc_ble_driver_py/lib/_nrf_ble_driver_sd_api_v5.so:
    @rpath/_nrf_ble_driver_sd_api_v5.so (compatibility version 0.0.0, current version 0.0.0)
    /Library/Frameworks/Python.framework/Versions/3.7/Python (compatibility version 3.7.0, current version 3.7.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1560.12.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.4)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.200.5)

Steps:

• Creating a python virtual environment (i.e. 3.7.6) using pyenv
  • pyenv install 3.7.6
  • pyenv virtualenv 3.7.6 my3.7.6
  • pyenv local my3.7.6
• Running nrfutil (dfu ble)
  • nrfutil dfu ble -pkg my_package.zip -ic MYNRF

Result:

The following segmentation fault occurs:

'nrfutil dfu ble -pkg my_packa…' terminated by signal SIGSEGV (Address boundary error)

[tesc]

Hi,

You are correct this has to do with that shared library file, yes. The link to the static path `/Library/Frameworks/Python.framework/Versions/3.7/Python (compatibility version 3.7.0, current version 3.7.0)` is not correct for your pyenv setup.

If using pyenv is of utmost importance, you can build pc-ble-driver-py from source, according to the steps in https://github.com/NordicSemiconductor/pc-ble-driver-py/blob/b8d22a6e4c146fedc13c8d5a330febe8a0df5795/azure-pipelines.yml#L54 , with the python installation part replaced by pyenv. See also the Building from source section of the pc-ble-driver-py readme.md.

We do not se any straight-forward way to fix this for our precompiled builds, so if using non-standard paths then I am afraid you must rely on building from source yourself.

Alternatively, I think you could maybe fix such pathing issues with symlinks as well, from erroneous hardcoded paths in the library file to the actual correct locations on your system...

Regards,
Terje