I see that you've solved it, Doug. But before we move on, can we please make it easier in the future to spot such a thing in the C code? What should be changed to get the C code trace ala Carp::confess? Can the taint checker figure out that the problem happens in the C code and not Perl and call something different than Perl_croak? I guess not. I'd prefer to have it segfault at the taint problem place (it dies in any case) so with debugger I could easily pinpoint the problematic code.
__________________________________________________________________ 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]
