On Tue, 14 Dec 1999, Saar Picker wrote:
>
> Hrm. Does perl use 0x 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 d
Hrm. Does perl use 0x 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
On Tue, 14 Dec 1999, Doug MacEachern wrote:
> On Tue, 14 Dec 1999, Saar Picker wrote:
>
> >
> > So I've been reading. I've actually then gone on to test it with a non-DSO
> > mod_perl and still get segfaults in the cleanup handling phase. I think
>
> is 'make test' core dumping or ? let's se
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 ==
0x
normally this is caused by duplicate
On Tue, 14 Dec 1999, Saar Picker wrote:
>
> So I've been reading. I've actually then gone on to test it with a non-DSO
> mod_perl and still get segfaults in the cleanup handling phase. I think
is 'make test' core dumping or ? let's see your perl -V too
So I've been reading. I've actually then gone on to test it with a non-DSO
mod_perl and still get segfaults in the cleanup handling phase. I think
the two errors may be related. I'm attaching The output from
MOD_PERL_TRACE=all (had to set PERL_FREE=0 since it was giving way too
many error messag
Hi,
After building apache with --shared-module=max and building mod_perl using
apxs, I get some strange behavior. I've also built my perl with -g
-DDEBUGGING.
On starting the web server, I get a bunch of "Bad free() ignored."
messages that seem to occur at the end of every block of perl code (i
