> Hi,
>
> I recently needed to study a bit the malloc/free functions for a project out
> of VC. I tested a few things out in VC express with a simple console program
> to have a beter in-depth view of the working. I found something strange when
> I allocated small amounts of bytes :
>
> If I do:
>
> malloc(10) let say for 100 times and run this functions afterwards
>
> void heapdump( void )
> {
>    _HEAPINFO hinfo;
>    int heapstatus;
>    hinfo._pentry = NULL;
>    while( ( heapstatus = _heapwalk( &hinfo ) ) == _HEAPOK )
>    { printf( "%6s block at %Fp of size %4.4X\n",
>         ( hinfo._useflag == _USEDENTRY ? "USED" : "FREE" ),
>           hinfo._pentry, hinfo._size );
>    }
>
>    switch( heapstatus )
>    {
>    case _HEAPEMPTY:
>       printf( "OK - empty heap\n" );
>       break;
>    case _HEAPEND:
>       printf( "OK - end of heap\n" );
>       break;
>    case _HEAPBADPTR:
>       printf( "ERROR - bad pointer to heap\n" );
>       break;
>    case _HEAPBADBEGIN:
>       printf( "ERROR - bad start of heap\n" );
>       break;
>    case _HEAPBADNODE:
>       printf( "ERROR - bad node in heap\n" );
>       break;
>    }
> }
>
> I get a "bad node in heap" ! If I do the same with fe
> malloc(1024) for 100 times the _heapwalk functions give no error and return
> with
> "OK - end of heap"
>
> I jus used the C RTL in the project nothing special. In the MSDN
> documentation I can't find anything on a minimum bytes or allignment limit.
>
> Anyone can bring up a light in this simpel example but odd result ?
>
> Many thks
> Guy