3   Debugging BASIC Program Lost, Sorry (PROLOSSOR)?    The Question is:    I I have a program written in Alpha BASIC which is basically a data server, M  communicating with users and servers via mailboxes. This program  is getting   the error:    N %BAS-F-PROLOSSOR, Internal error in DEC BASIC Run-Time Library.  Please submit  an SPR    J The exact same program is running on 50+ different CPU's which are runningO  anything from OpenVMS V7.2-1 to 7.3-2.  On 2 CPU's (both running OpenVMS 7.2-1 N  and BASIC V1.4), I am getting this message after the program has been running  for several hours to da ys.    L The program is linked with /TRACEBACK but no other messages a given when theN  program crashes. How can I go about trying to find where/what the problem is?  The Answer is :   >   Without additional details, it is not apparent if this error        Program Lost, Sorry    H   is a known problem with BASIC or the BASIC Run-Time Library, or withinG   underlying software, or within the application code itself.   Various G   of the more common causes of this error involve application-triggered 6   corruptions of memory; bugs in the application code.   H   There are ECO kits available for OpenVMS Alpha, and the OpenVMS WizardK   would encourage applying all available mandatory ECO kits for the OpenVMS E   release in use, and to ensure the most current version of the BASIC 0   compiler (V1.5, as of this writing) is in use.   : PROLOSSOR, Internal error in Alpha BASIC Run-Time Library.!   Please submit an SPR. (ERR=103) F Explanation: A consistency check in the BASIC run-time support failed.C   Program execution is aborted. This error cannot be trapped with a I   BASIC error handler unless the program contains OPTION HANDLE = SEVERE. I User Action: This error should never occur. Submit a Software Performance 	   Report.    F   After taking a look at the debugging information in topic (1661) andE   notes referenced there, please contact the support center, and make E   a formal report.  As referenced in topic (1661), faster systems and G   multiprocessing are some of the more common triggers that can uncover D   latent coding or timing-related, or memory synchronization errors.G   If/when you contact the support center, please expect to be asked for 8   the full source code and a way to reproduce the error.   0  Answer written or last revised on  30-APR-2004 