AIX system dump analysis Post: 303034707

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to do core dump analysis

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

2. UNIX for Advanced & Expert Users

Core Dump Analysis Using PStack and PMAP

Hello, I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ...

3. Solaris

use sunexplorer and vmcore analysis result instead of vmcore dump file itself.

in solaris 8 environment,frequently os panic happened and someone advise me check vmcore.:( for crash dump facility can we use SUNEXPLORER data collector package including with analyse result of vmcore like ? It may provides panic message included program counter address, perhaps ...

4. AIX

How to do core dump analysis in AIX?

Please tell me some methods to analyse core dump in AIX.:)

5. Red Hat

core dump analysis : __kernel_vsyscall ()

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...

6. UNIX for Dummies Questions & Answers

Learn Linux Core Dump Analysis

Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps?

LEARN ABOUT HPUX

cr_open

cr_open(3)						     Library Functions Manual							cr_open(3)

NAME

       cr_open() - open crash dump for reading

SYNOPSIS

DESCRIPTION

       The library call opens a crash dump and passes back a crash dump descriptor.

       The path argument points to a path name naming a crash dump directory or file, and must not exceed bytes in length.

       The CRASH * to which crash_cb points is set to a crash dump descriptor, which can then be passed to the other functions to access the crash
       dump.

       flags is a bitmask of zero or more of the following flag values, which affect the operation of future calls to libcrash routines  for  this
       crash dump, except for cr_verify(3), which has its own flags parameter.

       The library will not attempt to verify checksums of files in the crash
			     dump if this flag is set.

       The library will write messages to stderr during time-consuming operations
			     (decompressions and checksums) if this flag is set.

RETURN VALUE

       Returns zero for success.  Other possible return values are described in libcrash(5).

EXAMPLES

       The following call to opens crash dump contained in the directory and returns the crash dump descriptor For an example of reading the crash
       dump see the cr_read(3) manual entry.

AUTHOR

       was developed by HP.

SEE ALSO

       cr_close(3), cr_perror(3), libcrash(5).

																	cr_open(3)