STDUMP(1)							     STDUMP(1)

NAME    [Toc]    [Back]

     stdump - dump a file of intermediate-code debugging information

SYNOPSIS    [Toc]    [Back]

     stdump [-a] [-b] [-c]  [-g] [-h] [-i]  [-n	number]	file

DESCRIPTION    [Toc]    [Back]

     When compiling for	the old	32-bit ABI (-32), the compilers	generate an
     intermediate language which is separated into binary instructions and
     debugging information, each constituting a	separate file.	Use stdump to
     dump a file containing debugging information which	was generated by the
     compilers.	 stdump	writes to the standard output. The organization	of the
     output is simple but the details of the output are	complicated.  The
     detailed output is	be defined here. The output of stdump is subject to
     change and	one should not rely on the output format remaining the same
     from release to release.

     The organization of the output is:	 for each source file represented in
     file there	may be auxiliary-symbols, local-symbols, a file-indirecttable,
 optimization-entries, procedures, and line-numbers;	there is only
     one externals-table and one dense-number-table in file.

     By	default, stdump	prints all information about all sections of the
     debugging information.  The options (described below) restrict the	output
     to	the selected sections.

     The file may be an	object file (such as produced by cc -c)	or an
     executable	file (such as produced by ld(1)	or cc(1)) or a debugging
     information file (which may be produced as	described below).

     Normally, debugging information files (and	instruction files) are placed
     in	/tmp and removed after each compilation.  Use the -keep	option to cc,
     or	f77(1) to force	the compiler to	preserve these files in	the target
     directory.	 When this switch is used, the compilation of file.x (where x
     is	c for C	or f for FORTRAN, for example) will produce the	intermediate
     files file.B (instructions) and file.T (debugging information).  The
     latter file (file.T) may be used as input to stdump.

     The following options are recognized:

     -a	     Print the dense number table.  This section is empty for object
	     and executable files.

     -b	     Print the externals table.

     -c	     Print the local debugging symbols.	 The source file name is
	     printed here.

     -g	     Print the auxiliaries table.  This	table has encoded in it	in a
	     complex way the actual data types of all the data in the symbols.
	     The local-symbol and externals table sections show	this data
	     expanded into semi-readable text.



									Page 1






STDUMP(1)							     STDUMP(1)



     -h	     Print the line table.  One	source line number per 32-bits of
	     executable	code.

     -i	     Print the File Indirect Table.

     -n	number
	     Print information about only the source file whose	number is
	     given.  Files are numbered	sequentially starting with zero.

FILES    [Toc]    [Back]

     /tmp/ctmstaxxxxx default name of debugging	information file for process
		      id xxxxx

     file.T	      name of debugging	information file created by the	-keep
		      option

     /usr/bin/stdump  debugging	information dump program

SEE ALSO    [Toc]    [Back]

     elfdump(1), dwarfdump(1), cc(1), f77(1), pc(1), abi(5)

NOTES    [Toc]    [Back]

     One cannot	use stdump to display the debugging information	of 64-bit  (-
     64) or new	32bit ABI (-n32) object	files. Use dwarfdump(1)	instead.

     To	see the	linking	information, use elfdump(1) instead of stdump.


									PPPPaaaaggggeeee 2222