4.3BSD-Tahoe/usr/man/cat1/od.0

OD(1)		    UNIX Programmer's Manual		    OD(1)



NNAAMMEE
     od - octal, decimal, hex, ascii dump

SSYYNNOOPPSSIISS
     oodd [ -format ] [ file ] [ [++]offset[..][bb] [label] ]

DDEESSCCRRIIPPTTIIOONN
     _O_d displays _f_i_l_e, or it's standard input, in one or more
     dump formats as selected by the first argument.  If the
     first argument is missing, --oo is the default.  Dumping con-
     tinues until end-of-file.

     The meanings of the format argument characters are:

     aa	  Interpret bytes as characters and display them with
	  their ACSII names.  If the pp character is given also,
	  then bytes with even parity are underlined.  The PP
	  character causes bytes with odd parity to be under-
	  lined.  Otherwise the parity bit is ignored.

     bb	  Interpret bytes as unsigned octal.

     cc	  Interpret bytes as ASCII characters.	Certain non-
	  graphic characters appear as C escapes: null=\0,
	  backspace=\b, formfeed=\f, newline=\n, return=\r,
	  tab=\t; others appear as 3-digit octal numbers.  Bytes
	  with the parity bit set are displayed in octal.

     dd	  Interpret (short) words as unsigned decimal.

     ff	  Interpret long words as floating point.

     hh	  Interpret (short) words as unsigned hexadecimal.

     ii	  Interpret (short) words as signed decimal.

     ll	  Interpret long words as signed decimal.

     oo	  Interpret (short) words as unsigned octal.

     ss[n] Look for strings of ascii graphic characters, ter-
	  minated with a null byte.  _N specifies the minimum
	  length string to be recognized.  By default, the
	  minimum length is 3 characters.

     vv	  Show all data. By default, display lines that are
	  identical to the last line shown are not output, but
	  are indicated with an ``*'' in column 1.

     ww[n] Specifies the number of input bytes to be interpreted
	  and displayed on each output line. If ww is not speci-
	  fied, 16 bytes are read for each display line.  If _n is



Printed 7/9/88		 April 29, 1985                         1






OD(1)		    UNIX Programmer's Manual		    OD(1)



	  not specified, it defaults to 32.

     xx	  Interpret (short) words as hexadecimal.

     An upper case format character implies the long or double
     precision form of the object.

     The _o_f_f_s_e_t argument specifies the byte offset into the file
     where dumping is to commence.  By default this argument is
     interpreted in octal.  A different radix can be specified;
     If ``..'' is appended to the argument, then _o_f_f_s_e_t is inter-
     preted in decimal.  If _o_f_f_s_e_t begins with ``xx'' or ``00xx'',
     it is interpreted in hexadecimal.	If ``bb'' (``BB'') is
     appended, the offset is interpreted as a block count, where
     a block is 512 (1024) bytes.  If the _f_i_l_e argument is omit-
     ted, an _o_f_f_s_e_t argument must be preceded by ``++''.

     The radix of the displayed address will be the same as the
     radix of the _o_f_f_s_e_t, if specified; otherwise it will be
     octal.

     _L_a_b_e_l will be interpreted as a pseudo-address for the first
     byte displayed.  It will be shown in ``()'' following the
     file offset.  It is intended to be used with core images to
     indicate the real memory address.	The syntax for _l_a_b_e_l is
     identical to that for _o_f_f_s_e_t.

SSEEEE AALLSSOO
     adb(1)

BBUUGGSS
     A file name argument can't start with ``+''.  A hexadecimal
     offset can't be a block count.  Only one file name argument
     can be given.

     It is an historical botch to require specification of
     object, radix, and sign representation in a single character
     argument.

















Printed 7/9/88		 April 29, 1985                         2