nld and noft Manual

nld Diagnostic Messages
nld and noft Manual—520384-003
10-46
Fatal Errors
This is an internal error. Please contact your service provider.
**** ERROR **** [1203]:
The input object file named 'filename' appears to be
corrupted because the first (0) gp tables G_VALUE entry in
section 'name' does not have a G_VALUE of '0'. Instead, the
G_VALUE field is number.
**** ERROR **** [1204]:
The input object file named 'filename' appears to be
corrupted because the gp tables G_VALUE field in section
'name' at index number-1 is not in increasing order. Current
G_VALUE value is number-2. Previous G_VALUE value is
number-3.
**** ERROR **** [1205]:
The input object file named 'filename' appears to be
corrupted because the gp tables BYTES field in section 'name'
at index number-1 is not in increasing order. Current BYTES
value is number-2. Previous BYTES value is number-3.
**** ERROR **** [1206]:
You are trying to build a new version of an SRL with the
-prev flag, and there is now a procedure named name whose
entry vector uses number-1 bytes. However, in the previous
version of the SRL, the entry vector for this procedure used
number-2 bytes. This incompatibility is considered an error.
**** ERROR **** [1207]:
The input object file named 'filename' appears to be
corrupted because there is an inconsistency between the
procedure descriptor table and the relocation table. The
first procedure in this object file begins at virtual
address number-1, but there is a relocation site at number-2.
**** ERROR **** [1208]:
The input object file named 'filename' appears to be
corrupted because there is an inconsistency between the
procedure descriptor table and the relocation table. One
procedure in this file goes from virtual address number-1 to
number-2, and the next procedure starts at number-3, but
there is a relocation site at number-4.