On Mon, 11 Sep 2000, Bruce W. Hoylman wrote:
>
> I have a peculiar problem with a modperl module I have written. When
> migrating to the following configuration:
>
> perl, v5.6.0 built for sun4-solaris
> modperl_20000911162240 (1.2401)
> apache-1.3_20000911161201
>
> If I attempt to load the module in my startup.pl using:
>
> use Savvy::Moveform ();
>
> the server SIGSEGVs with the following stack trace:
looks like one of the 5.6.0 bugs, the Perl patch has been posted here
(don't have it handy), here's one that has also helped on the mod_perl
side, does it fix the problem for you?
--- perl_util.c~ Tue Jun 13 10:25:38 2000
+++ perl_util.c Tue Jun 13 11:16:45 2000
@@ -547,12 +547,14 @@
{
dTHR;
SV *sv = sv_newmortal();
+ COP *old_cop = curcop;
dTHRCTX;
sv_setpvn(sv, "require ", 8);
MP_TRACE_d(fprintf(stderr, "loading perl module '%s'...", name));
sv_catpv(sv, name);
perl_eval_sv(sv, G_DISCARD);
+ curcop = old_cop;
if(s) {
if(perl_eval_ok(s) != OK) {
MP_TRACE_d(fprintf(stderr, "not ok\n"));