Analyzing core dumps

[WSS]

Hi there ... Can someone please tell me the best way to analyze core dumps in HPUX and the syntax required? The core dump file is called "core"

I have tried gdb but with no luck. Which is the best way? (please include explanation with syntax) ....

Thanks in advance.
Trev

[mirco_1]

hy,

see
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=926632

DM.

[D Block 2]

Trevor,

you might want to look at the windows interface: wdb. This product also comes with gdb.

http://www.hp.com/go/wdb

[generic_1]

q4 analysis tool

[Eknath]

Hi Trevor,

Get q4 tool installed in you system. With help of q4 analysis tool you can analyse the core files...

Cheers!!!
eknath

[singvey]

# ps -ef | grep -i q4
root 2658 2643 1 12:08:59 pts/tb 0:00 grep -i q4
root 2610 1712 0 12:05:15 pts/ta 0:52 q4 -p
root 2625 2610 0 12:06:13 pts/ta 0:00 perl -- //.q4rc.pl 7 10 end of Q4 response 11.23

/usr/contrib/Q4/bin/q4


# q4 -p
@(#) q4 $Revision: 11.X B.11.23h Tue Jul 22 18:05:11 PDT 2003$ 0
Reading kernel symbols ...

Reading debug information...
Reading data types ...
Initialized ia64 address translator ...
Initializing stack tracer for EM...
script //.q4rc.pl

executable perl
version 5.008
SCRIPT_LIBRARY = /usr/contrib/Q4/lib/q4lib
perl will try to access scripts from directory
/usr/contrib/Q4/lib/q4lib

loaded misc2.pl
loaded misc.pl
loaded commands.pl
Loaded crashes.pl
loaded processors.pl
loaded globals.pl
loaded buf.pl
--------------------loaded--------------------
--------------------loaded--------------------
loaded spinlock_depth.pl
run Print_ProcState
loaded netinfo.pl
Get the latest Q4 news by typing "news | more".
q4>

q4> trace event 0 > trace
q4>
q4> include analyze.pl

q4> run Analyze AU >> /home/zxw/zxw.out
processing ...
................................................................................
done!
q4>

ï¼ grep â i hpmc zxw.out
"crash event was an HPMC"æ "Crash Event 0 (HPMC, struct crash_event_table_struct...

# grep -i crash zxw.out
crash_callback: calling function e000000000c67e80
crash_event_table: 0xe000000100007000
crash_processor_table: 0xe000000100004000
| Crash Processors |
cpt_crash_savestate 0xe0000001'008fdb70

| Crash Events | ä¸ é ¢æ ¯crasheventç æ è¿°
Crash Event 0 (INIT, crash_event_t at 0xe000000100007000):
Registers from the first crash event:
rp_crash_type 0x2
Stack trace from the first crash event:
crash event was a INIT

hope , this will help you