Hi,
Is there any way to find the mode of the binary file (debug or release) by analyzing the core file generated by that binary on the HPUX11i Platform?
Try using "nm" on the file to have a look at the symbols?
Is this 32bit or 64bit, PA-RISC or Itanium?
If 64bit or Itanium then elfdump may help.
Hi
In continuation to the previous query,
This is wat the core shows with the gdb cmd, I need to know whether the core is analysed with the correct version of GDB or the core is corrupted.
HP gdb 5.2 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.2 (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 `Hpux_xyz'.
Program terminated with signal 11, Segmentation fault.
Unknown si_code. Report to HP.
#0 0xc01700d4 in <unknown_procedure> ()
(gdb) where
#0 0xc01700d4 in <unknown_procedure> ()
warning: Attempting to unwind past bad PC 0xc01700d4
#1 0xcc410278 in <unknown_procedure> ()
(gdb) bt
#0 0xc01700d4 in <unknown_procedure> ()
#1 0xcc410278 in <unknown_procedure> ()
(gdb)
Do you know what program caused the core dump?
elfdump and odump will show contents of binary files.
What is your output of "uname -a"?
also try "man adb"
yes, v know the binary version, which caused the core dump but dont know in which mode it is built. v r using the same version of the binary to analyse the core, but unable to get the information from the core
Is there any way to analyse the core file ?
this is the o/p of uname -a
HP-UX sh1hp11i B.11.11 U 9000/800 872839660 unlimited-user license
elfdump or odump will tell you about the binary, not the core.
What do you mean by binary mode? Do you mean whether it has symbols or not?