On Wed, 28 Jun 2000 [EMAIL PROTECTED] wrote:
> The modperl archives are pretty clear that
> panic: POPSTACK errors
> caused by dies called in a eval is a perl bug.
>
> The archives are also clear that this is often a result
> of an interaction with Apache::Session, which I *was*
> getting, but have since fixed(?)
yes, fixed in Perl 5.6.0.
> My new problem is that I am getting the error
> between my PerlAccessHandler and HTML::Mason module.
> I repeat, the PerlAccessHandler is completely done, and
> the HTML::Mason handler hasn't been called at all.
> This is NOT a case of a tied Apache::Session going out
> of scope when the PerlAccessHandler ends.
> I think I proved this by putting debugging lines in
> subs DESTROY and 'save' of Apache::Session.pm.
>
> That's what my problem USED to be. :)
>
> Doesn't this mean it is happening in mod_perl itself?
maybe, are you still having this problem? if you can reproduce it, start
httpd like so:
% gdb httpd
(gdb) b Perl_my_exit
(gdb) run -X
then make a request that triggers the POPSTACK error, go back to gdb:
(gdb) where
and post the output of that.
