Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT




Loading

configASSERT( ( pxLink->xBlockSize & xBlockAllocatedBit ) != 0 );

Posted by cuixiaoxia632 on May 3, 2015

Hi:

I use heap4.c for my system memory management. now, I found that system halt some times and printf it halt in heap4.c line 281 configASSERT( ( pxLink->xBlockSize & xBlockAllocatedBit ) != 0 ); it seems that the system try to free memory which is not actually allocated. I wander to know in which case it will happen ? I check my code, pvPortMalloc and vPortFree are always implement in pair....

thank you in advanced.

Vincent


configASSERT( ( pxLink->xBlockSize & xBlockAllocatedBit ) != 0 );

Posted by heinbali01 on May 3, 2015

pvPortMalloc and vPortFree are always implement in pair...

That would be one explanation, calling vPortFree() too often.

Another explanation would be if you overwrite allocated memory. You asked for 1024 bytes and your code is using just a few more bytes.

You can also inspect pxLink->xBlockSize and see if it has a reasonable value.

Anyway, it looks like your code is causing corruption of the heap space, somewhere.

Regards.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS kernel V10 is available for immediate download. Now MIT licensed.


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS