To debug a program that contains p-code, make sure you set up CodeView with the p-code execution model. To do so, you will need a Model entry under the CodeView tag in TOOLS.INI.
The p-code execution model gives CodeView information about p-code instructions, addressing modes, registers, and so forth, which you need to debug p-code. With this execution model, you can debug p-code just as you can debug native machine code. Without the p-code execution model, you cannot view the source lines for p-code routines, unassemble p-code instructions, or view the p-code registers or stack. For information on the syntax of the Model entry, see topic .
There is a dynamic-link library (DLL) for each p-code execution model, depending on the operating environment. The following list shows the filenames of the DLLs and the environment with which they run:
Filename | Description |
NMD1PCD.DLL | Execution model for MS-DOS p-code |
NMW0PCD.DLL | Execution model for Windows p-code |
Specify the appropriate filename in the Model entry. For example, if you are debugging a Windows application that contains p-code, add an entry to the [CVW] section of TOOLS.INI such as:
Model:NMW0PCD.DLL
The exact syntax can vary, depending on your system configuration and other settings in TOOLS.INI.