<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/61736/sigsegv-address-boundary-error-running-nrfutil-or-pc-ble-driver-py-using-a-virtual-pyenv-environment</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Jun 2020 14:29:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/61736/sigsegv-address-boundary-error-running-nrfutil-or-pc-ble-driver-py-using-a-virtual-pyenv-environment" /><item><title>RE: SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment</title><link>https://devzone.nordicsemi.com/thread/256741?ContentTypeID=1</link><pubDate>Wed, 24 Jun 2020 14:29:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2eb5c09-fc39-450f-8280-5c6c05bddb0e</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;If using pyenv is of utmost importance, you can build pc-ble-driver-py from source, according to the steps in &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver-py/blob/b8d22a6e4c146fedc13c8d5a330febe8a0df5795/azure-pipelines.yml#L54"&gt;https://github.com/NordicSemiconductor/pc-ble-driver-py/blob/b8d22a6e4c146fedc13c8d5a330febe8a0df5795/azure-pipelines.yml#L54&lt;/a&gt; , with the python installation part replaced by pyenv. See also the &lt;a href="https://github.com/NordicSemiconductor/pc-ble-driver-py/blob/master/README.md#building-from-source"&gt;Building from source&lt;/a&gt; section of the pc-ble-driver-py readme.md.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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...&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment</title><link>https://devzone.nordicsemi.com/thread/253572?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 14:10:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f431f1e9-2e17-4477-a04c-4ac9600d716c</guid><dc:creator>dkkeller</dc:creator><description>&lt;p&gt;Thanks &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f44d.svg" title="Thumbsup"&gt;&amp;#x1f44d;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment</title><link>https://devzone.nordicsemi.com/thread/253570?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 14:06:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1960ee7c-dbb1-4d76-a190-f578a8b5209c</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am afraid I do not have any news to share regarding this issue, but I have asked the developers if they have looked into it and what they have to say about it. Sorry for the delay, this has taken a bit longer than what I originally anticipated. I will let you know as soon as I have something to share.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment</title><link>https://devzone.nordicsemi.com/thread/253437?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 07:55:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90caf720-6ba3-4740-8b65-59cf8633748c</guid><dc:creator>dkkeller</dc:creator><description>&lt;p&gt;Hi &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;,&lt;/p&gt;
&lt;p&gt;any news on this?&lt;/p&gt;
&lt;p&gt;Thanks in advance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SIGSEGV (Address boundary error) running nrfutil or pc-ble-driver-py using a virtual pyenv environment</title><link>https://devzone.nordicsemi.com/thread/251537?ContentTypeID=1</link><pubDate>Mon, 25 May 2020 14:45:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0b7c4f6-ee43-4209-bd37-770e6b84508a</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for the detailed descriptions. I have forwarded this to our developers for them to have a look, and hope to get back to you within a few days. I will let you know if we need more information. You are of course free to add more to this thread if you want to.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>