Hrm. Does perl use 0x55555555 as a marker? I thought once an sv was freed
it gets a null value or something. In any case, this shouldn't be
happening due to any strictly perl modules I'm loading. I am using
XML::Parser(::Expat) but I don't see why there should be interaction
between the two. Even when I comment the XML module out, segfaults still
occur. And there doesn't seem to be any problem when running the scripts
from the command-line. Isn't perl supposed to be smart enough not to try
and free variables which are already empty?
Anyways, any ideas on how I might proceed would be helpful.
-Saar
On Tue, 14 Dec 1999, Doug MacEachern wrote:
> I just looked closer at your attachement, so this is not 'make test', lots
> of stuff going on here, you must have had a working mod_perl at somepoint.
>
> as for the actually core dump:
> assertion botched (chunk's head overwrite?): ovp->ovu.ovu_rmagic ==
> 0x55555555
>
> normally this is caused by duplicate free() or similar bug in an extension
> or the library an extension is linked with. if you don't have purify,
> insure++ or similar, you'll need to start backing out some of your many
> modules to identify the culprit. one of the Perl -D options for malloc
> activity might help too.
>
