pmap will give you the process mapping of the application. It will provide details like which shared objects are in use, the memory usage for each of them et al.
pstack will give you the stack trace of a process.
You have a core dump with you. You are better off using gdb. Use it as
Hi All,
I am new to unix environment.
Please tell me how to do coredump analysis. Please explain clearly with example. What are the details are available in the core.
Thanks in advance (5 Replies)
How can we analyze a core file and determine why it was generated on a solaris system?
I know file core filename will tell us what program generated the file. But, what to do next to get more details?
Thanks, (5 Replies)
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc... (1 Reply)
Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.
I am using sparc 10... (4 Replies)
We have just enabled core dump on our RHEL5.7 OS. the java process is terminating very often so we enable core dump to analysis the issue and find below in core dump file.
Core was generated by `/usr/java/jdk1.6.0_06//bin/java -server -Xms1536m -Xmx1536m -Xmn576m -XX:+Aggre'.
Program... (0 Replies)
dear all,
i have p770 aix6.1
last week, the host reboot suddenly with dump. but i don't know how to analyze the dump.
I posted kdb details in the attachment.
please anybody help me.
#>kdb vmcore.0 /unix
vmcore.0 mapped from @ 700000000000000 to @ 7000001c72c0908
START ... (13 Replies)
Discussion started by: tomato00
13 Replies
LEARN ABOUT HPUX
pstack
pstack(1) General Commands Manual pstack(1)NAME
pstack - print a stack trace for each LWP in each process and core file
SYNOPSIS DESCRIPTION
prints a stack trace (hex+symbolic) for each LWP (Lightweight Process) in each process and core file.
Given the pid of a running process or the full path of a core file, prints the stack trace for each LWP thread in the process. To obtain
symbol information, searches load modules (executable and shared libraries) in the current directory, and You can specify the executable
path with the pid/corepath, separated by a colon character. If cannot find a load module, symbol information for frames in that module is
not displayed.
works by attaching to the running process and reading its registers, memory, and stack. Mismatch between executable and corefile may
result in unpredictable behavior.
Options
supports the following option:
Prints the usage menu.
Operand
supports the following operand:
pid identifies a running process, with an optional execpath, the full executable path.
corepath is the full path name of the specified executable.
RETURN VALUES
returns the following values:
Successful completion.
Failure.
An error has occurred.
SEE ALSO ldd(1), pldd(1).
Itanium(R)-based Systems Onlypstack(1)