ltrace man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

ltrace(1)							     ltrace(1)

NAME
       ltrace - trace inter-module procedure calls

SYNOPSIS
       logfile] executable argument]

   Remarks
       is  not	available on PA-RISC systems.  Currently is available only for
       32-bit applications on Integrity systems.

DESCRIPTION
       is a call tracing tool that traces  procedure  calls  across  different
       load  modules  in  an application (the executable on the command line).
       logs trace messages to a file.

       By default, logs messages to a file named which is created in the  cur‐
       rent  working  directory.   Trace messages can be logged to a specified
       file using the option.  Subsequent invocations of append the trace mes‐
       sages to the existing logfile even if the application is different.  To
       log messages in different files, use the option by specifying a differ‐
       ent filename at each invocation.

       shows  the  arguments in the procedure call if the load module is built
       in debug mode.  In addition, arguments of some commonly	used  routines
       are shown even if the debug version of is not available.

   Options
       recognizes the following options:

	      By default     creates  a	 file named to log the trace messages.
			     Use this option to specify a different  log  file
			     name for logging trace messages.  See

			     Subsequent	 invocations  of append the trace mes‐
			     sages to the existing logfile even if the	appli‐
			     cation  is different.  To log messages in differ‐
			     ent files, specify a different filename  at  each
			     invocation of the command.

	      Specify the argument(s) to be passed to the appli‐
	      cation.
			     Multiple arguments should be  given
			     within quotes.  See

EXTERNAL INFLUENCES
   Environment Variables
       uses the following environment variables to locate shared
       libraries.

	      These environment variables  can	be
	      used to specify the directories
			     to	 be  searched  for
			     library files at run‐
			     time.  The value is a
			     colon-separated  list
			     of	  paths	  of  such
			     directories.      For
			     more information, see
			     in dld.so(5)  or  the
			     option in ld(1).

       The  following  internationalization  vari‐
       ables affect the execution of

	      Determines the locale  category  for
	      native language, local customs,
			     and  coded	 character
			     set in the absence of
			     and other environment
			     variables.	 If is not
			     specified	or  is set
			     to an empty string, a
			     default  of  is  used
			     instead	of    (see
			     lang(5)).

	      Determines the values for all locale
	      categories and has
			     precedence	 over  and
			     other     environment
			     variables.

	      Determines the locale that should be
	      used to affect the format
			     and contents of diag‐
			     nostic messages writ‐
			     ten    to	  standard
			     error.

	      Determines the locale  category  for
	      numeric formatting.

	      Determines  the  locale category for
	      character handling functions.

	      Determines the location  of  message
	      catalogs for the processing of

       If  any	internationalization variable con‐
       tains an invalid setting, behaves as if all
       internationalization  variables	are set to
       See environ(5) for more	information  about
       environment variables.

RETURN VALUE
       returns	zero on success.  A non-zero value
       is returned in case of failure.

EXAMPLES
       In the following example,  creates  a  file
       named  in  the  current	working directory,
       traces procedure	 calls	to  all	 libraries
       used  by the application, and logs the mes‐
       sages in

       The file contains the following trace  mes‐
       sages:

       The  following invocation creates a logfile
       named to log the trace messages:

       The following invocation shows how to  pass
       the argument to the command being traced:

       The  following invocation shows how to pass
       multiple arguments:

AUTHOR
       was developed by the  Hewlett-Packard  Com‐
       pany.

FILES
       32-bit Integrity system dynamic loader

       64-bit Integrity system dynamic loader

       message catalog

ALSO SEE
   System Tools
	      ldd(1)	     Lists  dynamic depen‐
			     dencies of executable
			     files    and   shared
			     libraries.

   Miscellaneous
	      a.out(4)	     assembler,	 compiler,
			     and linker output.
	      dld.so(5)	     dynamic loader.

   Texts and Tutorials
Integrity Systems Only						     ltrace(1)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net