On Mon, 20 May 2002, Jason Gloudon wrote:
>
> The buflen of a new header was not always set to 0, which would cause SIGSEGVs
> when parrot_reallocate tries to copy a non-zero length buffer with a bufstart
> of NULL. This would happen when buffers get recycled.
>
> I don't know if new_pmc_header
The buflen of a new header was not always set to 0, which would cause SIGSEGVs
when parrot_reallocate tries to copy a non-zero length buffer with a bufstart
of NULL. This would happen when buffers get recycled.
I don't know if new_pmc_header has the same problem, but it also does not
initialize
