Thread safe memory allocation

dnadler wrote on Monday, August 19, 2019:

While it should not be necessary, with gcc you can override the non-weak
implementations using the linker “wrap” option.
See example in code here (though different functions are wrapped):

What processor and toolchain are you using?

On 8/19/2019 6:55 AM, Richard Damon wrote:

That sounds like your newlib was somehow build wrong or you system isn’t compatible with a right definition as the definitions in mlock are supposed to be weak, so are ok to be overriden by your copy. That probably needs to be taken up with the supplyer of your tools for the processor.

Thread safe memory allocation

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/freertos/discussion/382005/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/


Dave Nadler, USA East Coast voice (978) 263-xxx, xxx@xxx.com, Skype
xxxx.xxxx