core doesnt have back trace

[bhaskara]

Hi,
I have a coredump in my project.To see the back trace of the core I am unable to see any backtrace.

See below for more information and help plz me how to get the backtrace.

$./gdb nw3blkmx core

HP gdb 5.7 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.7 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Core was generated by `nw3blkmx'.
Program terminated with signal 6, Aborted.

#0 0xc0041cf8 in stat64+0xd90 () from /usr/lib/dld.sl
(gdb) bt
#0 0xc0041cf8 in stat64+0xd90 () from /usr/lib/dld.sl
warning: Attempting to unwind past bad PC 0xc0041cf8
#1 0xc00417e4 in stat64+0x87c () from /usr/lib/dld.sl
#2 0xc00417e4 in stat64+0x87c () from /usr/lib/dld.sl

[Srimalik]

which OS are u using ?


HP gdb 5.7 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00.

make me think that it is 32 bit gdb

and stat64 may mean that it is a core from 64 bit program,

I am not sure if 32 bit gdb will work with 64 bit core file...I may be wrong

I saw this problem some time back..but this was solved after I used the latest version of gdb. You are already using it.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1172464

there will be three binarie in the same gdb/bin folder

gdb , gdb32 and gdb64

try using gdb64 to see the core.

[Dennis Handly]

If you are getting signal 6 from dld.sl, there is nothing useful in the core or stack trace. In fact they fixed it so dld.sl commits suicide by signal 9 now. Did you get any error messages before it aborted? Perhaps unsats?
(I assume you are on the same system as the abort?)

>Srikrishan: stat64 may mean that it is a core from 64 bit program,

No, stat64 is the largefile version of stat(2).

[Srimalik]

I never used stat64. the name made me think that is something related with 64 bits.

But now i know. Thanks Dennis.

[Dennis Handly]

>Srikrishan: I never used stat64. the name made me think that is something related with 64 bits.

You don't directly. It is all done with macro games. It is has to do with 64 bit file offsets, in a 32 bit application.
http://www.docs.hp.com/en/5964-5283/ch02s09.html

[bhaskara]

Hi malik,
I am using HP-UX 11 and it is a 32 bit program.I am getting the same bt for 32 bit gdb(gdb32) also.I tried with 64 bit ,but it is thorwuing error because the format is different for 32 and 64 bit.