CRE Programmer's Guide

CRE Services
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
2-62
Using the Inspect, Native Inspect, and Visual Inspect
Symbolic Debuggers With CRE Programs
Using the Inspect, Native Inspect, and Visual
Inspect Symbolic Debuggers With CRE
Programs
This subsection describes how to use the Inspect, Native Inspect, and Visual Inspect
symbolic debuggers with programs that use the CRE, especially to locate where a
program is overwriting TNS CRE data.
The CRE and run-time libraries report several of the diagnostic messages shown in
Section 10, Run-Time Diagnostic Messages
if they find that their data has been
corrupted. Some of the messages you might see as a result of run-time library or CRE
data corruption are:
If the CRE or a run-time library reports a “Corrupted data” message, you can use any
symbolic debugger appropriate for the type of code to help isolate where the data is
being corrupted.
3nnn A call to FILE_OPEN_CHKPT_ failed. nnn is a file system error code.*
4nnn PROCESS_CREATE_ failed. nnn is a file system error code.*
Status codes between 4900 and 4999 represent the value returned by the
PROCESS_CREATE_ system procedure. The status code is established
by adding the number 4900 to the value returned by
PROCESS_CREATE_. See PROCESS_CREATE_ in the Guardian
Procedure Calls Reference Manual for more information on error codes
returned by PROCESS_CREATE_.
5000 There have been more than 10 failures by your program’s backup process.
The CRE does not attempt to start another backup process.
6000 An invalid parameter or other logic error was detected.
Message Number Message Text
11 Corrupted environment
12 Logic error
13 MCB pointer corrupt
15 Checkpoint list inconsistent
32 Invalid heap or heap control block
35 Heap corrupted
Table 2-10. Status Codes Returned by CRE Functions That Support Process
Pairs (page2of2)
Status Code Meaning
*The CRE converts file system error codes that are greater than 900 to 000.