Re: [Devel] NT crash in psaux

[Werner LEMBERG]

> What really leads to this crash is that when we get into
> PS_Table_Add(), we pass in "table" and "object".  Sometimes
> table->block and object point to the same piece of memory.  I
> haven't backtracked yet to see how we've gotten ourselves into this
> messy state.  The bottom line is that if table->cursor + length is
> greater than table->capacity, then we end up doing a realloc() on
> table.  If realloc() can't increase the existing memory chunk, then
> it will free it (leaving pointer object dangling) and malloc a new
> block of the desired size.  Then we go on to do the MEM_Copy() a few
> lines later, at which point NT/VC++ chokes when we try to read the
> unallocated memory object is still pointing at.

I've replaced the REALLOC() calls with ALLOC() + MEM_Copy().
Theoretically, the bug should be fixed now.


    Werner