I just downloaded the latest snapshot, and I see this file in the
sources, but make test doesn't seem to run it.. am I missing something?

On Wed, 2003-03-12 at 21:09, Stas Bekman wrote:
> David Morton wrote:
> > -------------8<---------- Start Bug Report ------------8<----------
> > 1. Problem Description:
> > 
> >   crypt returns wrong value even in prefork MPM setup. I see work has
> > been done on a workaround for threaded models, but I get the same
> > problem in a prefork model.
> > 
> >>From the command line, this works:
> > 
> > print crypt("testing", "SNXJvM5I.PJrE");
> > 
> > SNXJvM5I.PJrE
> > 
> >>From inside mod_perl, I get:
> > 
> > SNi9U6dA0Wi2M
> 
> David,
> 
> How do I reproduce this problem? I've added a test (get the latest cvs) and it 
> doesn't fail. Can you break this test?
> 
>    Revision  Changes    Path
>    1.1                  modperl-2.0/t/response/TestModperl/perl.pm
> 
>    Index: perl.pm
>    ===================================================================
>    package TestModperl::perl;
> 
>    # this test includes tests for buggy Perl functions for which mod_perl
>    # provides a workaround
> 
>    use strict;
>    use warnings FATAL => 'all';
> 
>    use Apache::Test;
>    use Apache::TestUtil;
> 
>    use Apache::Const -compile => 'OK';
> 
>    sub handler {
>        my $r = shift;
> 
>        plan $r, tests => 1;
> 
>        ok t_cmp("SNXJvM5I.PJrE",
>                 crypt("testing", "SNXJvM5I.PJrE"),
>                 "crypt");
> 
>        Apache::OK;
>    }
> 
>    1;
>    __END__
> 
> 
> 
> 
> 
> 
> 
> __________________________________________________________________
> 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