zar@XHMEIA.CALTECH.EDU (Perfect Tommy) (09/17/86)
Has anyone come across a situation where the VMS DEBUGger dies with... %DEBUG-I-NOMSG, message number 00028093 %DEBUG-W-NOMSG, message number 00028332 %DEBUG-E-NOMSG, message number 00028334 (VMS V4.4, FORTRAN V4.5 -- some of the code was compiled under earlier FORTRAN versions greater than or equal to V4.3) Thanks for any comments or guesses where to look... From The Humble Zar
carl@CITHEX.CALTECH.EDU (Carl J Lydick) (09/21/86)
This looks similar to a problem I once ran into when trying to debug a HUGE program: in that instance, the program's virtual memory was expanded to the extent that it overwrote parts of the debugger. How big is your program? Since the debugger is giving the wrong severities for the status codes (they should be I, E, and F, respectively), this could well be your problem.