FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [October 2014 Threads] Problems with pvPortMalloc/vPortFreePosted by llapisera on October 31, 2014 Hello.
I have problems when I allocate memory for using as a temporal buffer. My application
makes something like this:
MyStruct *p;
p = (MyStruct*)pvPortMalloc(sizeof(MyStruct));
if (p == NULL) {
return SOME_ERROR;
}
// Use the region allocated
// finally free memory
vPortFree((void*)p);
If this is executed one time, there's no problem. But sometimes when memory is freed
the data are corrupted (data outside the heap). It seems pvPortMalloc has reserved blocks
of memory outside the heap region. Does anyone seen this behavior?
Currently I'm working with heap_4.c and FreeRTOS v7.3.0.
Thanks in advance.
Problems with pvPortMalloc/vPortFreePosted by rtel on October 31, 2014 The most likely cause is a good old fashioned memory corruption.
When a block is allocated a structure is placed at the start of the block that notes the length of the block. The value returned by pvPortMalloc() jumps over the structure, so the application writer should never see or access it, or even know it is there.
vPortFree() uses the structure to know how to free the memory. It is likely that the information in the structure has been overwritten by something, causing the memory to be freed incorrectly.
Recent FreeRTOS versions include a configASSERT() statement to test for that occurring (as far as is possible), but as you are using an older version it might be that the assert() is not present in your code.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|