The best way to get this information from a core dump is by using the ServerDoc tool, described here. Unless there is a problem running the automated tool, that should be used instead of these manual steps. In rare circumstances it can be useful to analyze a coredump on a different machine, but in User Commands proc(1) NAME proc, pflags, pcred, pldd, psig, pstack, pfiles, pwdx, pstop, prun, pwait, ptime proc tools man pages section 1: User Commands October 2012.
This section describes the commands and utilities available with this operating system, including commands found only in the SunOSBSD Compatibility Package, commands for communicating with other systems, commands associated with the Form and Menu Language Interpreter (FMLI), and commands specific to the SunOS system. The available STRACE(1) General Commands Manual STRACE(1) NAME top strace trace system calls and signals and received numerous additions and improvements in syscalls decoders on Linux; strace development migrated to git during that period.
Since If you have a bug report for this manual page, send it to 12 TOP Command Examples in Linux. by Ravi Saive Published: March 4, 2013 Last Updated: 4 Free Shell Scripting eBooks. This is the part of our Pstack linux manual commands series of commands in Linux. 18 Tar Command Examples in Linux; 20 Linux YUM (Yellowdog Updater, Modified) Commands DOCUMENTATION: Solaris specific commands to run when troubleshooting core files for NetBackup support cases Solution.
Manual: Veritas NetBackup (tm) 6. 0 Troubleshooting Guide for UNIX and Windows# pstack core tmppstack. out# pmap core tmppmap. out pstack(1) print a stack trace of running processes. pstack(1) man page RedHat 9 (Linux i386) Linux Commands CentOS 7. 0 man page for pstack (centos section 1) GSTACK(1) Linux Programmer's Manual GSTACK(1) NAME gstack print a stack trace of a running process SYNOPSIS gstack pid DESCRIPTION gstack attaches to the active process named by the pid on the command line, and prints out an execution stack trace.