AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.

 View Only
  • 1.  How to do core dump analysis in AIX

    Posted Fri July 18, 2008 08:26 AM

    Originally posted by: SystemAdmin


    Please tell me some methods to analyse the cause of core dump in AIX.


  • 2.  Re: How to do core dump analysis in AIX

    Posted Fri July 18, 2008 01:17 PM

    Originally posted by: alethad


    From past experience IBM is pretty tight lipped about telling you how to analyse a core dump. You will have to open a PMR if you want details.

    One thing you can do is to look in your errpt -a output. It usually tells you the name of the program or routines that were running when the core dump occurred. These may or may not have been the cause of the core dump though.

    Good luck.


  • 3.  Re: How to do core dump analysis in AIX

    Posted Fri July 18, 2008 02:41 PM

    Originally posted by: SystemAdmin


    Hello,

    From the IBM Cert Study Guide.

    9.3.5 Analyzing system dumps
    The kdb command allows you to examine a system dump or a running kernel.
    The kdb command interprets and formats control structures in the system and
    provides miscellaneous functions for examining a dump.

    For example, to invoke the kdb command using a dump file named
    /var/adm/ras/vmcore.0 and the kernel file named /unix, type:
    1. kdb /var/adm/ras/vmcore.0 /unix

    Regards, Leo.


  • 4.  Re: How to do core dump analysis in AIX

    Posted Fri August 09, 2013 02:37 PM

    Originally posted by: danielsan


    kdb is used to review OS dumps, i.e. system crash or forced dump. 

    dbx, idebug or gdb can be used to review an application core files.

    Regards



  • 5.  Re: How to do core dump analysis in AIX

    Posted Fri July 18, 2008 02:51 PM


  • 6.  Re: How to do core dump analysis in AIX

    Posted Sat July 19, 2008 05:00 AM

    Originally posted by: j.gann


    -> find out which signal caused the core dump: file core_file

    -> find out where the program was executing when the coredump occured (program's call stack):
    dbx object_file core_file
    where

    dbx comes with bos.adt.debug and offers many more subcommands -> man dbx

    Joachim Gann