checkobj(1) [bsd man page]

CHECKOBJ(1)						      General Commands Manual						       CHECKOBJ(1)

NAME

       checkobj - check an object file to see whether it can be executed

SYNTAX

       checkobj [ -s ] [ -f ] [ -40 ] [ file ... ]

DESCRIPTION

       Checkobj attempts to determine whether the named files are valid executable binary files.  It checks for size restrictions, including those
       due to the granularity of memory management on the PDP11.  It is especially useful for overlaid object files, where there are a	number	of
       constraints.   If a file is too large or improperly laid out, checkobj attempts to point out format changes that would allow the program to
       run.

OPTIONS

       Several options control the checks:

       -s     Check for the use of separate I/D.  If the file is separate executable, an error is flagged, and an appropriate way to  load  for  a
	      nonseparate machine is suggested if possible.

       -f     Check for the use of floating point arithmetic without inclusion of the floating-point interpreter.

       -40    Combine the -s and -f options, to check for suitability for an 11/40-class PDP11.

BUGS

       The  test for floating point is simple-minded.  It is based on the definition of ``fltused'' by the C compiler and ``fptrap'' in the float-
       ing-point simulator.  This test does not work if the object has been stripped.

DIAGNOSTICS

       The exit status is 0 if all named files are runnable with the specified options, nonzero otherwise.

AUTHOR

       Mike Karels, University of California, Berkeley

3rd Berkeley Distribution													       CHECKOBJ(1)

TRAPOV(3F)																TRAPOV(3F)

NAME

       trapov - trap and repair floating point overflow

SYNOPSIS

       subroutine trapov (numesg, rtnval)
       double precision rtnval

DESCRIPTION

       NOTE:  This  routine  applies  only to the older VAX 11/780's.  VAX computers made or upgraded since spring 1983 handle errors differently.
       See trpfpe(3F) for the newer error handler.  This routine has always been ineffective on the VAX 11/750.  It  is  a  null  routine  on  the
       PDP11.

       This call sets up signal handlers to trap arithmetic exceptions and the use of illegal operands.  Trapping arithmetic exceptions allows the
       user's program to proceed from instances of floating point overflow or divide by zero.  The result of such operations will  be  an  illegal
       floating point value.  The subsequent use of the illegal operand will be trapped and the operand replaced by the specified value.

       The  first  numesg  occurrences of a floating point arithmetic error will cause a message to be written to the standard error file.  If the
       resulting value is used, the value given for rtnval will replace the illegal operand generated by the arithmetic error.	Rtnval must  be  a
       double precision value. For example, ``0d0'' or ``dflmax()''.

FILES

       /usr/lib/libF77.a

SEE ALSO

       trpfpe(3F), signal(3F), range(3F)

BUGS

       Other arithmetic exceptions can be trapped but not repaired.

       There  is no way to distinguish between an integer value of 32768 and the illegal floating point form.  Therefore such an integer value may
       get replaced while repairing the use of an illegal operand.

4.2 Berkeley Distribution					   May 15, 1985 							TRAPOV(3F)