| MP2081missing native entry code for function at segment:offset |
|
| |
MPC detected a p-code function that was called from native code but does not have a valid native entry-code sequence. |
| |
To find the function that caused this error, look up the given map address in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
This error can be caused by using #pragma native_caller( off ) or the CL /Gn command-line option when defining functions that are exported. |
| |
Recompile and relink the module that contains the function at the specified map address, making sure that native entry code is generated, then relink the executable file. |
| MP2082missing native entry code for exported function at segment:offset |
|
| |
MPC detected an exported p-code function that does not have a valid native entry code sequence. All exported p-code functions must have native entry code sequences. |
| |
To find the function that caused this error, look up the given map address in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
This error can be caused by using #pragma native_caller( off ) or the CL /Gn command-line option when defining functions that are exported. |
| |
Recompile and relink the module that contains the function at the specified map address, making sure that native entry code is generated, then relink the executable file. |
| MP2083calling convention inconsistency: source segment:offset, target segment:offset |
|
| |
The calling convention of the function reference at the given source map address was inconsistent with the calling convention in the function defined at the target map address. |
| |
To find the functions that caused this error, look up the given map addresses in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
Check the consistency of the function prototypes used in the given functions. Recompile the appropriate modules and relink. |
| MP2084parameter length inconsistency: source segment:offset, target segment:offset |
|
| |
The length of the actual parameters of the function reference at the given source map address was inconsistent with the length of the formal parameters of the function defined at the target map address. |
| |
To find the functions that caused this error, look up the given map addresses in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
Check the consistency of the function prototypes used in the given functions. Recompile the appropriate modules and relink. |
| MP2085inconsistent reference made to the function at segment:offset |
|
| |
One or more inconsistent references were made to the function at the specified map address. Either the calling convention or parameter length was inconsistent. |
| |
To find the function that caused this error, look up the given map address in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
Check the consistency of the function prototypes for the function at the given map address and all references to that function. Recompile the appropriate modules and relink. |
| MP2086p-code version mismatch: compiler version1, MPC version2 |
|
| |
The versions of the compiler and MPC that were used are incompatible. Make sure that compatible versions of the compiler and MPC are used when generating p-code programs. |
| |
This error can occur when there are multiple versions of the compiler or MPC in the path. Check the path to make sure that the correct versions are being used. |
| |
Either recompile the modules using the appropriate compiler or rerun the appropriate version of MPC. |
| MP2087p-code version mismatch: p-code interpreter version1, MPC version2 |
|
| |
The versions of PCD.LIB and MPC that were used are incompatible. Make sure that compatible versions of the p-code interpreter library and MPC are used when generating p-code programs. |
| |
This error can occur when there are multiple versions of the p-code interpreter or MPC in the path. Check the path to make sure that the correct versions are being used. |
| |
Either relink using the appropriate version of PCD.LIB or rerun the appropriate version of MPC. |