PROBLEM: (57545, 77428, 81750, 81751,
          83165, 84829, 89529, 90030, 90424,
          91329, 92149, 92758, 93693, 93909,
          95259) (PATCH ID: OSF540-332)
********
This patch corrects problems in the dbx and object file tools: dbx, ostrip, 
strip, mcs, dis, cord, file, and stdump.
  dbx

     - When reading an incomplete core file, dbx erroneously reports a
       "cannot attach to loader" error.  With this patch, dbx now issues a
       warning when it detects an incomplete core file.
     - For some applications that use Fortran runtime libraries, dbx will 
       core dump during initialization.  (This problem was first seen with 
       an application using Fortran V5.5-1877-48BBF runtime libraries, but 
       it occurs infrequently.)  This problem has been fixed.
     - After a debugged application has forked, dbx loses track of the
       breakpoints set by the user.  These breakpoints can neither be listed
       nor deleted, but remain in effect.   The patch corrects this problem
       by modifying dbx to restore the appropriate breakpoints when a
       process switch occurs.

  ostrip 

     - ostrip -m reported a fatal error such as "aux_indice mapping 
       nil...".  This problem has been corrected.
     - A failure while processing an object prevented ostrip from processing
       additional objects on the link line.  This problem has been fixed.
     - ostrip does not process all of the options on the command line.  For
       example, "ostrip -cjtxz ..." processes only the -j option and
       ignores the remaining options.  With this patch, these options are 
       now processed in the following order: -j, -c, -x, -t, and -z.
     - ostrip terminates with the fatal error "File offsets overlap" for
       executables that have been instrumented by Atom-based tools such as 
       pixie, third, or hiprof.  This has been corrected.


  strip 

     - For executables that have been instrumented by Atom-based tools such
       as pixie, third, or hiprof, strip terminates with the fatal error 
       "File offsets overlap."  This has been corrected.

  mcs 

     - For executables that have been instrumented by Atom-based tools such
       as pixie, third, or hiprof, mcs terminates with the fatal error
       "File offsets overlap."  This has been corrected.


  dis 

     - The disassembly output source file name was incorrect for source 
       lines occuring in header files.  This has been corrected.
     - The disassembly output source file previously showed incorrect 

       procedure names for object files with source lines occuring in
       header files.  This has been corrected.
     - The "clrfen" pal call was disassembled as "0xae".  With this 
       patch, the disassembler will now display it as "clrfen".
     - Some nop (no-operation) instructions were incorrectly disassembled 
       as "esr26" or "esr28" pseudo-ops.  With this patch, the disassembler
       will display these nops as "lda" and "ldah" instructions.

 cord 
     - Previously, the cord tool did not warn the user about unsupported 
       object types such as OMAGIC and NMAGIC files.  Users are now warned
       not to use cord on these unsupported object file types.
     - cord did not update file-descriptor addresses in the symbol table.  
       This has problem has been fixed.
     - cord does not preserve segment padding for objects built
       with the linker's -disk_block option. This problem has been 
       fixed. 

 file 

     - A memory leak caused the file command to fail and report "no aouthdr"
       error messages when ~300 or more objects were processed in one 
       command.  This problem has been fixed.

 stdump 

     - A small memory leak caused stdump to occassionaly fail and report an 
       "I/O error" message.  If the heap size was limited to less than 100 mB,
       this error occurred when 1000 or more objects were processed in one  
       command.  This problem has been fixed.