This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

malloc failing

Hi,
I currently encounter problems with malloc.
I use microlib and configured the heap to be 32MBytes (0x02000000 bytes).
Under some special circumstances (depending on the image date we get from a CMOS) malloc fails somwhere in my image analysis when trying to allocate memory of e.g. 0x1000 bytes. I tracked the total amount of allocated memory and found out, that only 0x19000 bytes has been allocated until the call of malloc.
After each call to the image analysis functions, all allocated memory is freed, thus it should not be caused by fragmentation.

How can it be possible, that malloc fails?
May it be possible - because of a programming error -, that overwriting some data malloc uses to determine the free amount of memory, will cause such problems?

Where can I get informations on how microlib implements malloc?

Parents
  • Something else to consider is the implications of having assembler-written ISR that fails to save one or more registers. Depending on what registers that gets trashed in the ISR, large parts of the main application can continue to work.

    A x86 processor has quite few registers, so a corrupted register quickly kills a program. The ARM has a lot of registers so in some situations you can have large code blocks that rely on the contents of a specific register.

Reply
  • Something else to consider is the implications of having assembler-written ISR that fails to save one or more registers. Depending on what registers that gets trashed in the ISR, large parts of the main application can continue to work.

    A x86 processor has quite few registers, so a corrupted register quickly kills a program. The ARM has a lot of registers so in some situations you can have large code blocks that rely on the contents of a specific register.

Children