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.
may be we should check that we have Apache-Test when building mp2, as we rely on having the right version to have the tests pass.
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.
Is it related to the failure noise you get at the server startup?
Do you remember the last time you run it w/o a problem? e.g. try checking out earlier dates and try to find when the problem was introduced.
The weird startup errors were caused by the wrong Apache::Test version (as far as I can tell), that problem is history now.
t\filter\in_bbs_inject_header.t always succeeds when run as part of the whole "nmake new" run, and only sometimes crashes Apache when run alone, which was only uncovered by last night's SMOKE run.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
