Analyze core dump
 
*
Welcome, Guest. Please login or register. November 22, 2008, 04:33:35 AM


Login with username, password and session length


Pages: [1]   Go Down
  Print  
Author Topic: Analyze core dump  (Read 1561 times)
0 Members and 1 Guest are viewing this topic.
Michael
Administrator
Hero Member
*****
Posts: 526


« Reply #3 on: January 17, 2007, 12:36:15 PM »

kdb should work for both - and is included in AIX automatically. There is a "SERVER" mode kdb (only in maintanence mode I think. There is somethiong to make is 'special') appropraitely named KDB (all caps).

dbx is, I assume, the preferred debugger by app developers. But once you get into application development you must also be aware of  java debuggers, or any other interpreted application environment. Otherwise you just have a core dump of the "engine", not the application you are working on.

As a category, these tools are known - in IBMSpeak - as ADE - Application Development Environment ( http://www.pcmag.com/encyclopedia_term/0,2542,t=ADE&i=37532,00.asp ). More recently the DK names are being used - or XXX Development Kits.

Thanks for the update! Reminders help!
Logged
ubihga
Registered
*
Posts: 1


« Reply #2 on: January 17, 2007, 11:25:45 AM »

Hi

I think kdb is for systemdump.

A core file is an application dump, here yoy need dbx.

/HGA
Logged
Michael
Administrator
Hero Member
*****
Posts: 526


« Reply #1 on: January 12, 2007, 04:43:22 PM »

Been a long while.

The basic command you will want is 'kdb' - kernal debugger.

The most basic commands to see what is in the dump are:

stat
status
errpt

and dont forget help.

There is a redbook, not sure how current - and I'll have to look up the number.
Logged
mvh
New Member
*
Posts: 3


« on: January 11, 2007, 02:54:11 PM »

I would like to better understand how to analyze a core dump.  Normally I just send it to IBM software support,and they reply.  Can anyone provide any local system commands that will give me an idea what actually caused the core dump.  errpt -a |more shown the application and other information, but is there a way to see what command / process was being attempted that caused the issue?

Thanks in advance.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM
Page created in 0.496 seconds with 18 queries.




eXTReMe Tracker

Terms of Use and Privacy and Security Policies
Copyright 2001-2008 Michael Felt and ROOTVG.NET