At 11:03 AM +0100 2/23/03, Vorl�nder, Martin wrote: >But: after realcleaning & rebuilding, deinstalling PERLSHR and >deassigning all logicals and symbols, Perl 5.8.0 still gives me >7 failed tests, with an ACCVIO on at least the first two. The >debug session of t/run/switches up to the failure is in the >attached file.
I don't see anything in your configuration that raises a red flag. I also can't reproduce the accvio on a very similar configuration. I think we really need to see the stack trace and start looking at what's under the hood. If you can reproduce the accvio in miniperl, the quickest way (without waiting all day to rebuild the entire thing in debug on your DEC 3000), would be to: $ mms/macro=__DEBUG__=1 dbgminiperl.exe $ mcr []dbgminiperl t/run/switches.t or of course just hack descrip.mms to give you a link/traceback. Once you know where in the C code the accvio occurs, you can rebuild that one module in debug, relink miniperl, and watch what's going on in the VMS debugger. You can always add one module at a time in a minute or two if you need others. This is the approach I use all the time on older machines where a complete debug build might take a couple of hours. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
