This manual page is part of Xcode Tools version 3.2.2

To obtain these tools:

If you are running a version of Xcode Tools other than 3.2.2, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.



jstack(1)                                                                                          jstack(1)



NAME
       jstack - stack trace

SYNOPSIS
       jstack [ option ] pid
       jstack [ option ] executable core
       jstack [ option ] [server-id@]remote-hostname-or-IP

DESCRIPTION
       jstack  prints  Java  stack  traces of Java threads for a given Java process or core file or a remote
       debug server. For each Java frame, the full class name, method name, 'bci' (byte code index) and line
       number,  if  available, are printed. With the -m option, jstack prints both Java and native frames of
       all threads along with the 'pc' (program counter). For each native frame, the closest  native  symbol
       to  'pc',  if  available, is printed. C++ mangled names are not demangled. To demangle C++ names, the
       output of this command may be piped to c++filt.

       NOTE - This utility is unsupported and may or may not be available in future  versions  of  the  J2SE
       SDK.  jstack is not currently available on Windows platforms or on the Linux Itanium platform.

PARAMETERS
       Options are mutually exclusive. Option, if used, should follow immediately after the command name.

       pid            process  id  for  which  the  stacktrace is to be printed.  The process must be a Java
                      process. To get a list of Java processes running on a machine, jps may be used.

       executable     Java executable from which the core dump was produced.

       core           core file for which the stack trace is to be printed.

       remote-hostname-or-IP
                      remote debug server's (see jsadebugd) hostname or IP address.

       server-id      optional unique id, if multiple debug servers are running on the same remote host.

OPTIONS
       -m             prints mixed mode (both Java and native C/C++ frames) stack trace.

       -h             Prints a help message.

       -help          Prints a help message.

SEE ALSO
       pstack(1) c++filt(1) jps(1) jsadebugd(1)

KNOWN BUGS
       Mixed mode stack trace, the -m option, does not work with the remote debug server.



                                                13 June 2004                                       jstack(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you? Yes It's good, but... Not helpful...