You can chat about native SDK questions and issues here.

User avatar
By Agentsmithers
#80991 Hi Everyone, Anyone knows the underlying reason on why or how malloc and zalloc hang when exhausted out of memory vs. returning NULL or failure. It's hanging at that point then the WDT kicks off and if I disable the WDT both Software and Hardware it hangs forever and never returns. I was hoping it just needed more time to run logic to find space to allocate however that is not the issue. Any insight would be extremely helpful! :)
Thank you!!
User avatar
By Agentsmithers
#81192 I answered my own question only after donating a few days of my life.
If you Malloc or Zalloc X amount of bytes and write to destination X+1 you can overwrite a boundary pointer and the next call to Malloc/Zalloc will hang forever then trigger the WDT. Cheers =.=