C:\Dev\test\perl\bin\perl.exe -Iblib\arch -Iblib\lib t/TEST -clean C:\Dev\test\perl\bin\perl.exe -Iblib\arch -Iblib\lib t/TEST -bugreport -verbose=0 "my" variable $script masks earlier declaration in same scope at C:\Dev\src\modperl-2.0\t\response\TestApache\subprocess.pm line 64. Compilation failed in require at C:/Dev/test/perl/site/lib/Apache/TestConfigPerl.pm line 593.
I'm not sure if this would cause this, but it's picking up some modules under your installed Perl tree (C:/Dev/test/perl/), rather than using that under C:\Dev\src\modperl-2.0\. Perhaps there's an incompatibility? Can you try moving the installed mp2/Apache-Test files away while doing the tests to see if that helps?
Ah, I just noticed that there's no "Apache-Test" directory in modperl-2.0 pulled from CVS. So for my regular Apache/Perl installations Apache::Test 1.13 from the Perl lib was used (probably got there via an earlier snapshot?), while for the debug Apache/Perl installation Apache::Test 1.12 from the Perl lib (installed from CPAN) was used, which apparently caused all the weird errors. I've now checked out a copy of Apache-Test in the modperl-2.0 directory.
Not that it helps any. I can now run in_bbs_inject_header.t and it crashes just like with the regular builds, but JIT debugging with MSVC6 only shows the same useless Asm etc. as before, no useful stacktrace or anything that I can see. Last time that I've used this debugger was for single-threaded MFC apps, so maybe I just don't know how to handle cases like this.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
