new returning null

Follow

Andrew Fraser

• October 17, 2015 13:42

I am writing firmware in C++ and am finding that quite quickly any call to new returns null.

I have allocated 32768 bytes of heap so even if I have a memory leak would not expect new to fail to allocate memory so quickly.

Does anyone have any thoughts on what I might be missing ?

Andy

0

• 

  Michael Johnson

  • October 21, 2015 06:56

  Do you have 32K of SRAM? Could it be a stack size problem?

  0

  Comment actions Permalink
• 

  Andrew Fraser

  • October 21, 2015 18:09

  Sorry, I forgot to mention that I am using a STM32F215RGT6 with 112KBytes of SRAM.

  I am not too familiar with how new / delete work in Crossworks - is the full heap available for object allocation ?

   

  Andy

  0

  Comment actions Permalink
• 

  Michael Johnson

  • October 22, 2015 07:51

  The heap section is allocated by the linker based on the heap size project property. You can use the symbols browser to see the address ranges of the heap section.

  0

  Comment actions Permalink

Please sign in to leave a comment.