.Title CMem_Message, VMS Messages for C Heap Debugger .Ident "V1.1" .Facility CMEM, 161/Prefix=CMEM__ .Severity Success Normal ! ! Everything worked. Don't worry about it! ! .Severity Informational Init ! ! This informational message is simply meant to let the user know that ! the debugging code was linked with the image and that at least one ! piece of code has invoked our routines. ! Timestamp /FAO=1 ! ! Sometimes it is handy to have a timestamp with the message. ! StackEna StackDis TimeEna TimeDis BndryPrtEna BndryPrtDis RelMemPrt RelMemReuse ! ! The user can change how the software operates on the fly. These ! messages simply alert the user to the state change. ! .Severity Warning mallocFail ! ! As a result of the user calling the 'malloc' routine, we tried to ! expand the virtual address space and failed. We will return a NULL ! pointer to the calling routine. ! FreeUnallo ! ! The calling routine attempted to release memory that was never ! allocated. The address specified by the caller is displayed. ! FreeWrtFail ! ! The memory being released shows signs that someone modified memory ! before that location in memory. ! NoBndyPrt ! ! The user may request that freed memory be protected. That ability ! is only available for blocks which have been allocated using ! boundary protection. This warning message is displayed because we ! are currently not in that mode (although we could have some previously ! allocated blocks in the protected memory zone). ! UnExpResp /FAO=2 ! ! We check the number of lines returned from the debugger subprocess in ! response to some CMEM requests. This message simply means that we ! didn't get the expected response. The program will display the text ! which was returned. ! .Severity Error ProtChgFail ! ! A call to $SETPRT has failed. The exact status from that call should ! be displayed following this message. ! DeltVAFail ! ! We had some sort of weird error trying to release memory. ! BndryRdVio /FAO=1 BndryWrtVio /FAO=1 ! ! The process has incurred an access violation. The attempted read or ! write was into a protected page surrounding one of segments of ! allocated memory. We display any info we have about the segment. ! .Severity Fatal InfoExpFail ! ! We had run out of slots for holding information about 'malloc' ! requests. A call to LIB$GET_VM has failed. ! UnexpErr /FAO=1 ! ! An error occurred which really should never happen. Refer to the ! associated error text to see what failed. ! GetVMFail /FAO=1 ! ! A call to LIB$GET_VM failed. This usually means we're out of virutal ! address space or else there is some form of memory corruption. ! ExpRegFail ! ! An error was returned from $EXPREG ! NoFreeBlk /FAO=1 ! ! There were no free blocks within the cluster when the count of free ! blocks was greater than zero. This represents a programming error. ! OldSubPrc ! ! We did a $FORCEX on an old sub-process but it did not die. ! SubCreFail ! ! LIB$SPAWN failed ! ArrTooSml ! ! The debugger returned more lines than was expected. ! UnDbgExit ! ! The subprocess exited unexpectedly. The completion status is also ! reported. I bet it is a quota problem... ! .End