1. Messages
  2. C library re-entrancy under Zephyr

Re: C library re-entrancy under Zephyr

Rob Meades
 

Thanks for the swift response. That's a shame. I will go look at the PR at your link as shifting to the re-entrant versions just for Zephyr is going to be painful.

Rob

-----Original Message-----
From: users@lists.zephyrproject.org <users@lists.zephyrproject.org> On Behalf Of Kumar Gala
Sent: 11 March 2021 17:54
To: Rob Meades <Rob.Meades@u-blox.com>
Cc: users@lists.zephyrproject.org
Subject: Re: [Zephyr-users] C library re-entrancy under Zephyr

*** This is an EXTERNAL email. It was sent from outside of u-blox. ***

Re-entrant support between newlib and zephyr is not currently supported.

There’s an old PR on the subject

https://github.com/zephyrproject-rtos/zephyr/pull/21518

- k

On Mar 11, 2021, at 11:51 AM, Rob Meades via lists.zephyrproject.org <Rob.Meades=u-blox.com@lists.zephyrproject.org> wrote:

Should I expect C library functions (e.g. strtok()) under Zephyr to be re-entrant or must I call the re-entrant versions (i.e. in this case strtok_r())?

I ask because I am building/running nRF52840 (cortex-m4) and strok() _appears_ to NOT be re-entrant: I'd like to understand if this is expected or if I've messed up a configuration somewhere. My prj.conf file is attached in case it is helpful in answering the question.

Rob





<prj.conf>
Join users@lists.zephyrproject.org to automatically receive all group messages.