On Tue, 14 Dec 1999, Saar Picker wrote:
>
> Hrm. Does perl use 0x55555555 as a marker?
yes, see malloc.c
> I thought once an sv was freed it gets a null value or something.
sure, but with Perls before 5.005_60-ish, Perl's malloc overrides system
malloc/free *everywhere*, not just for Perl data, but also for other C
code using malloc/free in the same runtime
> In any case, this shouldn't be happening due to any strictly perl
> modules I'm loading.
true, but pure Perl can't be ruled out as triggering such a bug.
it might help if you can run your server under gdb and post a stacktrace
after this core dump.
