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 FREEBSD
gcore
GCORE(1) BSD General Commands Manual GCORE(1)NAME
gcore -- get core images of running process
SYNOPSIS
gcore [-f] [-s] [-c core] [executable] pid
DESCRIPTION
The gcore utility creates a core image of the specified process, suitable for use with gdb(1). By default, the core is written to the file
``core.<pid>''. The process identifier, pid, must be given on the command line.
The following options are available:
-c Write the core file to the specified file instead of ``core.<pid>''.
-f Dumps all available segments, excluding only malformed and undumpable segments. Unlike the default invocation, this flag dumps map-
pings of devices which may invalidate the state of device transactions or trigger other unexpected behavior. As a result, this flag
should only be used when the behavior of the application and any devices it has mapped is fully understood and any side effects can
be controlled or tolerated.
-s Stop the process while gathering the core image, and resume it when done. This guarantees that the resulting core dump will be in a
consistent state. The process is resumed even if it was already stopped. The same effect can be achieved manually with kill(1).
FILES
core.<pid> the core image
HISTORY
A gcore utility appeared in 4.2BSD.
BUGS
Because of the ptrace(2) usage gcore may not work with processes which are actively being investigated with truss(1) or gdb(1). Addition-
ally, interruptable sleeps may exit with EINTR.
The gcore utility is not compatible with the original 4.2BSD version.
BSD July 14, 2010 BSD