Introduction |Translating | Debugging | Performance | fpx messages | fpxr messages

This appendix contains a list of all the fpxr messages and suggested user actions, if any.

The severity levels are as follows:

Messages and user actions

The error messages and suggested users actions for fpxr are as follows:

filename is not an fpx-translated executable

Severity level: Fatal

Explanation: The specified executable was not produced by FreePort Express.

User action: Do not attempt to use fpxr to provide a run-time environment for anything other than executables translated by fpx.

 

filename is not a valid executable file

Severity level: Fatal

Explanation: You attempted to run fpxr on a file that was not the output of FreePort Express.

User action: Verify that the file you are trying to execute is a valid translated executable from FreePort Express.

 

filename uses fpxr interface Vn; this version of fpxr supports Vn

Severity level: Fatal

Explanation: The executable was translated by using a version of fpx that is not supported by the version of fpxr installed on the system.

User action: Ensure that the latest versions of fpx and fpxr are installed on the system, and retranslate the executable.

 

Attempt to issue getpgrp() on other than current process

Severity level: Fatal

Explanation: The executable attempted to find the process group number for a process other than itself. This is possible in SunOS, but is not allowed by Digital UNIX because it creates a minor security hole in the system. The fpxr environment returns the process group ID of the current process to the executable, but the executable may not perform as expected.

User action: There is no fix for this problem.

 

Bad getsysinfo() op 0xhexinteger

Severity level: Warning

Explanation: The executable did a getsysinfo() system call by using an operation code or argument that fpxr does not support. The fpxr environment ignored the call, but the executable may not perform as expected.

User action: There is no user fix for this error. Submit an informational bug report to Digital. The unsupported operation will be considered for inclusion in a future release of FreePort Express.

 

Bad setsysinfo() op 0xhexinteger

Severity level: Warning

Explanation: The executable did a setsysinfo() system call by using an operation code or argument that fpxr does not support. The fpxr environment ignored the call, but the executable may not perform as expected.

User action: There is no user fix for this error. Submit an informational bug report to Digital. The unsupported operation will be considered for inclusion in a future release of FreePort Express.

 

Bad signal handler address 0xhexinteger

Severity level: Fatal

Explanation: While executing a sigvec() system call on behalf of the translated executable, the address of the signal handler routine could not be expressed in 32 bits. This condition should never occur. If it does, it indicates a severe problem in FreePort Express.

User action: File a bug report.

 

Called fpxr stub routine name

Severity level: Warning

Explanation: The translated executable attempted to use a feature of fpxr that is not yet implemented.

User action: File a bug report.

 

Cannot specify both FPXR_VERBOSE and FPXR_QUIET

Severity level: Fatal

Explanation: The current environment has both the FPXR_VERBOSE and the FPXR_QUIET variables set. Because these are conflicting operations, fpxr cannot perform both at the same time.

User action: Use only one of them during run time.

 

Error loading executable

Severity level: Fatal

Explanation: This message indicates that a problem occurred that prevented loading the translated executable, either due to an I/O error or due to a format error in the translated executable itself. Normally, this message will occur with some other error message that explains the reason for the problem.

User action: Retranslate the executable to ensure that you have a complete and correctly translated executable. Verify that there is enough disk space on the target system to hold the complete executable. Try executing the retranslated executable. If this problem persists, file a bug report.

 

Error opening file filename

Severity level: Fatal

Explanation: While being run with FPXR_GENERATE_FEEDBACK set, fpxr could not create or open the feedback .hif file. This could be due to:

User action: You can do any of the following:

Executable has unsupported a.out magic number 0octalinteger

Severity level: Fatal

Explanation: The input executable is not supported by FreePort Express. FreePort Express does not support OMAGIC files.

User action: Submit an informational bug report to Digital. The unsupported file type will be considered for inclusion in a future release of FreePort Express.

 

Executable uses minus-infinity rounding; better performance may be achieved by retranslating with the -fixround option. Consult the user manual for further details.

Severity level: Warning

Explanation: This error message suggests that better performance might be realized by using the -fixround option, at the possible expense of some precision.

User action: The suggested user action is to translate with -fixround running the executable again to determine if the performance is better and the precision is acceptable.

 

fpxr currently supports only the BSD programming environment not integer

Severity level: Warning

Explanation: The translated executable attempted to use the setsysinfo() system call to change the programming environment to something other than BSD. The fpxr environment only supports the BSD programming environment. If this condition is detected, fpxr will not change the programming environment and will not return an error to the caller. The executable may or may not behave as expected afterward.

User action: Submit an informational bug report to Digital. The unsupported operation will be considered for inclusion in a future release of FreePort Express.

 

fpxr does not yet support pure-COFF files

Severity level: Fatal

Explanation: FreePort Express currently supports only a.out COFF files, that is, COFF files that have an a.out header as the optional header. This is what SunOS generates. FreePort Express does not support pure COFF files, those for which there is no optional header.

User action: None required. Pure COFF files cannot be translated or run.

 

fpxr has run out of heap space

Severity level: Fatal

Explanation: The fpxr environment attempted to perform a dynamic memory allocation on its own behalf and failed. Because fpxr's dynamic memory requirements are fairly modest, this error almost certainly indicates a "memory leak" somewhere in fpxr.

User action: File a bug report.

 

Ignoring close of file descriptor integer

Severity level: FPXR_INFO

Explanation: The executable tried to close a file descriptor that must remain open for fpxr to function. This is only informational, and is suppressed when the environment variable FPXR_QUIET is set.

User action: None required. Setting the environment variable FPXR_QUIET suppresses this message.

 

Internal error in writing hif entry

Severity level: Warning

Explanation: This is an internal FreePort Express error.

User action: Submit a bug report.

 

Interpreter attempted to branch to invalid SPARC address 0xhexinteger

Severity level: Fatal

Explanation: The interpreter attempted to branch to an address that is not part of the process's address space or that does not contain valid SPARC code.

User action: Check the operation of the executable against the original untranslated version; this type of behavior is reported under SunOS as a "segmentation fault." Also, verify that all of the support files and environment requirements for the application are present on the Alpha system. If the error is still reported, there may be an internal problem in the fpx translator. File a bug report.

 

ioctl request code is not supported

Severity level: Warning

Explanation: The executable did an ioctl() system call by using a code that fpxr does not recognize or support. The fpxr environment ignored the ioctl call, but the executable may not perform as expected.

User action: There is no user fix for this error. Submit an informational bug report to Digital. The unsupported request will be considered for inclusion in a future release of FreePort Express.

 

No executable file specified

Severity level: Fatal

Explanation: The command fpxr was used without -V or -help, and without specifying a translated executable to run.

User action: Specify a translated executable to run.

 

Nonstandard open flags 0octalinteger while opening filename.

Severity level: Warning

Explanation: The executable did an open() system call by using flags that fpxr does not support. The fpxr environment ignored the unsupported flags, but the executable may not perform as expected.

User action: There is no user fix for this error. Submit an informational bug report to Digital. The unsupported flags will be considered for inclusion in a future release of FreePort Express. Note that some flags to open() under SunOS have no corresponding meaning by Digital UNIX, and thus may be unsupportable.

 

No PTYs available for xterm I/O

Severity level: Fatal

Explanation: The FPXR_XTERM environment variable was set, but fpxr was unable to allocate a pseudoterminal for the xterm to use.

User action: Try closing some of the other terminal windows on the workstation, or rebuild the OSF system with more PTY devices.

 

SIGFPE backtracked to nonfloating instruction @ 0xhexinteger

Severity level: Fatal

Explanation: An arithmetic exception occurred, but when attempting to trace back to the faulting instruction, it appeared as though the fault was generated by an instruction that did not include floating-point calculations. It is therefore likely that the code was not generated according to the rules for floating-point recovery.

User action: Translate the executable with the -full_fp option to allow recovery from floating-point faults. If you have done this and this error is still reported, please file a bug report so that -full_fp can be fixed.

 

SIGFPE occurred @0xhexinteger but instruction does not have software

completion enabled

Severity level: Fatal

Explanation: An arithmetic exception occurred and was successfully traced back to the faulting instruction, but that instruction did not have the /S qualifier enabled. This indicates that the instruction did not expect to generate an exception that would require recovery.

User action: Translate the executable with the -full_fp option to allow recovery from floating-point faults. If you have done this and this error is still reported, please file a bug report so that -full_fp can be fixed.

 

SIGFPE occurred @0xhexinteger but instruction emulation yields no exceptions

Severity level: Fatal

Explanation: An arithmetic fault occurred and was successfully traced back to the faulting instruction, but no condition could be found that would have generated the fault.

User action: Translate the executable with the -full_fp option to allow recovery from floating-point faults. If you have done this and this error is still reported, please file a bug report so that -full_fp can be fixed.

 

SIGFPE occurred @0xhexinteger but register write mask is zero

Severity level: Fatal

Explanation: An arithmetic fault occurred, but the register write mask provided by the system has no bits set. According to the Alpha architecture, at least one bit in this register must be set when an arithmetic fault occurs.

User action: This error indicates a problem in either the hardware, the operating system, or fpxr. Submit a bug report.

 

SIGFPE occurred, cannot backtrack to faulting instruction PC =0xhexinteger exc summ = 0xhexinteger register mask = 0xhexinteger

Severity level: Fatal

Explanation: A floating-point exception occurred, but fpxr cannot find the faulting instruction within the basic block where the fault was detected.

User action: Translate the executable with the -full_fp option to allow recovery from floating-point faults. If you have done this and this error is still reported, please file a bug report so that -full_fp can be fixed.

 

SPARC Syscall 'name' is not supported

Severity level: Warning

Explanation: The executable attempted to perform a system call that fpxr recognizes but currently does not support. The fpxr environment ignored the call, but the executable may not perform as expected.

User action: There is no user fix for this error. Submit an informational bug report to Digital. The unsupported system call will be considered for inclusion in a future release of FreePort Express.

 

The translated executable attempted a floating-point calculation with a denormalized number or NaN. Retranslate using the -full_fp option to fpx.

Severity level: Fatal

Explanation: The translated executable attempted a floating-point calculation with a denormalized number or a Not-a-Number (NaN). Most SunOS SPARC executables complete such a calculation without generating a SIGFPE, but the Alpha architecture always generates a trap (and subsequent SIGFPE) for such calculations. To emulate the quiet completion of such calculations, the translated executable must be able to recover from the SIGFPE. The -full_fp option must be set during translation.

User action: Retranslate using the -full_fp option. If you have done this and this error is still reported, please file a bug report so that -full_fp can be fixed.

 

Unable to allocate vfork synchronization channel

Severity level: Fatal

Explanation: The executable did a vfork() system call, and fpxr was unable to allocate a file descriptor to synchronize the parent and child processes.

User action: Submit a bug report.

 

Undefined system call number integer

Severity level: Warning

Explanation: The executable attempted to perform a system call that fpxr does not know about or support. The fpxr environment ignored the call, but the executable may not perform as expected.

User action: There is no user fix for this error, but it is unlikely that the executable would run properly on an SunOS SPARC system. If it runs properly on SunOS, please submit a bug report.

 

Unknown ioctl request 0xhexinteger

Severity level: Warning

Explanation: The executable did an ioctl() system call by using a code that fpxr does not know about or support. The fpxr environment ignored the ioctl call, but the executable may not perform as expected.

User action: There is no user fix for this error. Submit an informational bug report to Digital. The unsupported request will be considered for inclusion in a future release of FreePort Express.

If you have questions about FreePort Express, send email to fpx-info@scrugs.lkg.dec.com.

Click to send feedback