GDB 6.0 core: not in executable format: File format not recognized

[ShivS]

Hi Dennis,

I increased the core dump size to unlimited using the following command:

ulimit -c unlimited.

After this, the core that was produced was of size 4337787128 (i.e. 4.04 GB).

The elfdump gave me the following error:
elfdump -S -o core
elfdump: I/O error: core Value too large to be stored in data type (elfdumperr 2501)

However, now the HP gdb (version 6.0) is working fine and I am able to debug as shown below:

gdb issueHolders core
Detected 64-bit executable.
Invoking /opt/langtools/bin/gdb64.
HP gdb 6.0 for PA-RISC 2.0 (wide), HP-UX 11i
and target hppa2.0w-hp-hpux11.00.
Copyright 1986 - 2009 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 6.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 `issueHolders'.
Program terminated with signal 10, Bus error.
BUS_UNKNOWN - Unknown Error

warning: Load module /opt/oracle/product/9.2.0/lib/libclntsh.sl.9.0 has been stripped.
Debugging information is not available.


warning: Load module /opt/oracle/product/9.2.0/lib/libwtc9.sl has been stripped.
Debugging information is not available.

#0 0x40000000001ae2d4 in ItemList::initPass (this=0x0, val=false) at itemList.cc:142
142 numSorted = 0;
(gdb) where
#0 0x40000000001ae2d4 in ItemList::initPass (this=0x0, val=false) at itemList.cc:142
#1 0x400000000008e800 in IssueHolders::processHoldings (this=0x8000000100006058) at issueHolders.cc:478
#2 0x400000000008c274 in IssueHolders::runReport (this=0x8000000100006058, req=0x800003ffefff2b68) at issueHolders.cc:215
#3 0x4000000000078288 in issueHolders (transb=0x80000001000a12d0) at issueHolders.cc:107
#4 0xc00000000116d840 in _tmsvcdsp+0xce0 () from /opt/bea/tuxedo8.1/lib/libtux.sl
#5 0xc00000000118fae4 in _tmrunserver+0x1dc () from /opt/bea/tuxedo8.1/lib/libtux.sl
#6 0xc00000000116c668 in _tmstartserver+0x1e8 () from /opt/bea/tuxedo8.1/lib/libtux.sl
#7 0x4000000000077628 in main (argc=14, argv=0x800003ffefff1d20) at BS-4b6e.c:76
Current language: auto; currently c++
(gdb) frame 0
#0 0x40000000001ae2d4 in ItemList::initPass (this=0x0, val=false) at itemList.cc:142
142 numSorted = 0;
(gdb) list
137 //---------------------------------------------------------------------------
138 // initPass() - initializes the pass[] array to the given value
139 //---------------------------------------------------------------------------
140 void ItemList::initPass(bool val)
141 {
142 numSorted = 0;
143 memset(pass, val, maxItems * sizeof(bool));
144 }
145
146 //---------------------------------------------------------------------------
(gdb)


So looks like my problem is solved.

But can you please let me know why elfdump is giving that error and how should I solve that?

Thanks in advance.

Shiv.

[Dennis Handly]

>So looks like my problem is solved.

You mean just the fact you can now debug? :-)
Your "this" pointer can't be NULL.

>But can you please let me know why elfdump is giving that error and how should I solve that?

Make sure you have the latest linker patch, PHSS_39749. Unfortunately there is nothing obvious where it says largefile (> 2 Gb) corefiles is fixed. Only my initial enhancement where it works on core files.

[ShivS]

Hi Dennis,

Thanks for patch information. I will apply it on my system.

Thanks again!
Shiv

[ShivS]

The HP GDB 6.0 is working fine on my system and I am able to debug core files now.

Thanks
Shiv