https://devzone.nordicsemi.com/f/nordic-q-a/43044/malloc-returns-valid-pointer-even-if-heap-size-is-set-to-0Hello. I need a bit of help with my case. I have nRF52832 dev kit. I have set heap size to zero in Makefile: And even with that change I am still able to allocate memory using malloc(). Here is the code: And this is the result: So malloc(en-USTelligent Community 13Sun, 27 Jan 2019 16:43:08 GMThttps://devzone.nordicsemi.com/thread/168099?ContentTypeID=1Sun, 27 Jan 2019 16:43:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:745538d5-da09-4256-95e4-ef62917bb6ceera<p>Do you mean that newlib&#39;s malloc implementation has such obvious bug? It&#39;s hard to believe that it allows to allocate more memory than exists on the device.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/168074?ContentTypeID=1Sun, 27 Jan 2019 01:10:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:66b5a47d-55f9-4099-b8de-a702e987a8beRK<p>It&#39;s not allocating memory, it&#39;s a bug in the malloc implementation which is a very simple malloc. You can look at the source code and see this.</p><div style="clear:both;"></div>