Re: segfault in 2.0RC1, didn't happen in 1.99_16?

[prev] [thread] [next] [Date index for 2004/12/24]

> Tyler, have you by chance read:
> http://perl.apache.org/docs/2.0/user/help/help.html#Resolving_Segmentation_Faults
> plus the short script that we can reproduce the problem with.

	Maybe... I'll look into it in more detail later. My main point was
that no segmentation fault occurs in 1.99_16, so something must have changed
in the last two revisions that has introduced this behaviour (whether it's a
problem with mod_perl, or the way my script has been using it all along that
just surfaced with the new version). I've upgraded mod_perl many times on
this server and never had this particular problem, and of course have
recompiled everything (apache2, other modules, etc) in the same, correct
order as always.

	I did do a backtrace, and can tell you that the error occured in
Perl_sv_setflag... If I muster up the courage to try this again, I'll send
you the entire trace.

> It's never a good idea to upgrade a production server, w/o first testing 
> the new software on the staging machine. Please read this section in 
> chapter 5 of "Practical mod_perl":

	Hah! :) I need a good staging machine first. I guess I could set it
up on my home system, but I've got all sorts of other crazy stuff happening
there (daily debian-unstable upgrades, mod_bt testbed, etc) that might get
in the way.

	Either way, as soon as I get a chance to test it more, I will and
will get you more info, either how I solved the problem or why I can't solve
it. :)

	- Tyler


        -- 
        Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html