Geoffrey Young wrote:

Joe Schaefer wrote:

Joe Schaefer <[EMAIL PROTECTED]> writes:



1. Problem Description:

Current cvs segfaults w/perl 5.8.5, not reproducible with 5.8.4:

#0  0x0000002a9682334b in Perl_safesysmalloc (size=24) at util.c:78
78              my_exit(1);

This may be an ithread-related bug in 5.8.5, not mp2.

% t/TEST -v t/directive/cmdparms.t


Any assembler gurus out there?  This is starting to look
like a gcc/ld bug on my debian-amd64 box now...


fwiw, I don't see this error on my 5.8.5 threaded perl (-V below), but I'm
not using the same system (or processor) you are.  I don't know if anything
else stands out...

Same here, i686 and no segfault.

What the assembly dump is helpful for? do you think the C function wasn't compiled properly? I think that it's quite possible that some other memory corruption occuring early simply affects this particular frame. If you always hit the same address, try setting a watchpoint for it and see if anything touches it beforehand?

Also try to minimize the test (and various httpd.conf/modperl_extra.pl blocks) to a very minumum and then may be it'll be easier to find the cause.

--
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to