Error debugging Oracle core

[José Enrique González]

Hi:

I have downloaded WDB to my HP-UX 11.23 box (last version) to debug an Oracle core. But when trying to do so, I get this:

# gdb /oracle/SAC/920_64/bin/oracle /oracle/SAC/admin/cdump/core_27014/core
HP gdb 5.4.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.4.0 (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 `oracle'.
Program terminated with signal 6, Aborted.


warning: Load module /oracle/SAC/920_64/lib//libodm9.so has been stripped.
Debugging information is not available.


warning: Load module /oracle/SAC/920_64/lib//libskgxp9.so has been stripped.
Debugging information is not available.


warning: DWARF Error: wrong version (0x4, expected 2) in compilation unit header of /oracle/SAC/920_64/lib//libjox9.so.
#0 0xc00000000031b890:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
(gdb) bt
#0 0xc00000000031b890:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
BFD: BFD internal error, aborting at ../../../Src/gnu/gdb/dwarf2read.c line 7722 in unsigned long long read_address(struct _bfd *, char *)

BFD: Please report this bug.

#

Any help available is truly appreciated.

Jose Enrique Gonzalez
Caracas, Venezuela

[Jini Susan George · Accepted solution]

Hi,

This error is seen due to the oracle library being compiled with an older compiler. This is caused due to a corrupted executable/shlib/object file which in turn is caused by older compilers. The right solution is to get a libjox9.so compiled using the latest compilers. Meanwhile, there are 2 workarounds to this problem at the cost of hindering debuggability of this library.

1. Stripping the debug info from this library using the "strip -l libjox9.so" command. (It would be prudent to save a copy before doing this).

2. Try:
(gdb) set src-no-g none
(gdb) file a.out
You need to load the executable after the src-no-g is set.

Do let us know if this helps.

Regards,
Jini.

[José Enrique González]

Thanks a lot! I applied the second solution and succesfully could get the stack trace. However, using this procedure, messages warning about libraries being stripped are also shown; I checked the pointed binaries and no modifications were actually done to them, so I think I could apply number 1 safely (I'll check it in a test environment)