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] [November 2013 Threads]
Hello,
i have a question about function
static void prvInsertBlockIntoFreeList(xBlockLink *pxBlockToInsert)
is it possible to be value off pxBlockToInsert->xBlockSize some huge number like 23608965
Is this normal to get in some conditions or this is done by some memory corruption. Device it seems to work on normal after that.
To me it seems is more something gone wrong, but i just want to be sure. I looked some code and i found that maybe could happen on "normal" mode too.
Best regards,
Dan
The top bit of the xBlockSize member is set to indicate the block is owned by the application. When the block is freed the code checks the top bit is set (as part of a sanity check that the block has not already been freed), then the bit is cleared before the block is added back into the free heap.
So, yes, it is expected that the member will contain a huge number while the block is allocated.
Regards.
Thank you for explanation! Much clearer now!
Thread can be closed now
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.