Core Dump With SIGINT on ia64 (479 Views)
Reply
Occasional Visitor
deepaks_2
Posts: 3
Registered: ‎03-31-2011
Message 1 of 7 (479 Views)

Core Dump With SIGINT on ia64

Hi,

We have an application which uses Pro*c daemons, which was running perfectly fine on HP-UX PA-RISC, we migrated it to ia64. And since then we are having problems with this, after every 5 days or so the process is generating the core dump. This process now connects to oracle 11g database and earlier it was connecting to 8i. And if look into the core file it has very limited information.

Below is the more information about the core file.

file core
core: ELF-64 core file - IA64 - received SIGINT


strings core
xl@
xz@
I/opt/oraclient/product/11.1.0/client_64/lib/libclntsh.so.11.1
!lfvinit
1/usr/lib/hpux64/libnss_files.so.1


Can anyone please suggest what could be the issue here.

Thanks.
Honored Contributor
Viktor Balogh
Posts: 1,007
Registered: ‎03-15-2009
Message 2 of 7 (479 Views)

Re: Core Dump With SIGINT on ia64

> which uses Pro*c daemons, which was running perfectly fine on HP-UX PA-RISC, we migrated it to ia64

are you using the Itanium version of that daemon? What does a file command to the binary says?
****
Unix operates with beer.
Occasional Visitor
deepaks_2
Posts: 3
Registered: ‎03-31-2011
Message 3 of 7 (479 Views)

Re: Core Dump With SIGINT on ia64

Yes it is the itanium version of the process which is now producing the core dump.

Below is the output of the file command.

file npconfset
npconfset: ELF-64 executable object file - IA64
Honored Contributor
Viktor Balogh
Posts: 1,007
Registered: ‎03-15-2009
Message 4 of 7 (479 Views)

Re: Core Dump With SIGINT on ia64

the strings can be a misleading command to analyze a core file, you can list the used libs like this:

# what core

and to debug:

# gdb npconfset core

http://www.hp.com/go/wdb
****
Unix operates with beer.
Occasional Visitor
deepaks_2
Posts: 3
Registered: ‎03-31-2011
Message 5 of 7 (479 Views)

Re: Core Dump With SIGINT on ia64

Hi Viktor,

Thanks for your reply, the problem is that the core is generated by the prodcution process and i can not run the gdb on prodcution machine.

Below is the output of what command.

core:
B1
HP Port of Compaq Convert RTL V0.0.00
HP Fortran of Alpha RT V0.0.00
Intel Fortran RTL V1.1-929 1+ 1-Aug-2003
$ PATCH_11.23/PHCO_38637 Apr 19 2009 23:47:50 $
$ PATCH_11.23/PHCO_39205 Apr 16 2009 20:40:54 $
HP DCE/9000 1.9 PHSS_38258 Module: libdcekt.so.1 Date: Nov 14 2008 10:14:42
rec_seq.c 8.2 (Berkeley) 9/7/93
$RCSfile: environment.c,v $ $Revision: /main/HPDCE02/HPDCE_64/1 $ (OSF) $Date: 1997/11/06 19:44 UTC $
libXOM 1.9 (BULL S.A) 7/1/92
Pthread Interfaces
$ B.11.23 Aug 8 2004 00:39:58 $
92453-07 linker dld HP Itanium(R) B.12.55
92453-07 linker uld HP Itanium(R) B.12.55
Honored Contributor
Viktor Balogh
Posts: 1,007
Registered: ‎03-15-2009
Message 6 of 7 (479 Views)

Re: Core Dump With SIGINT on ia64

> the problem is that the core is generated by the prodcution process and i can not run the gdb on prodcution machine.

there is the packcore feature of gdb which helps you pack everything on the prod system and lets you analyze it on a test system. see here:

http://h21007.www2.hp.com/portal/download/files/unprot/wdb/wdb_6.2/GDB.pdf

p.194: "Generating core files with packcore /unpackcore/getcore"
****
Unix operates with beer.
Acclaimed Contributor
Dennis Handly
Posts: 25,206
Registered: ‎03-06-2006
Message 7 of 7 (479 Views)

Re: Core Dump With SIGINT on ia64

>Can anyone please suggest what could be the issue here.

There is nothing we can do without first getting a stack trace.

>the problem is that the core is generated by the production process and I can not run gdb on production machine.

Why not? You aren't going to run the program, just look at it with gdb.

>Viktor: there is the packcore feature of gdb which helps you pack everything on the prod system and lets you analyze it on a test system.

Right. But while you are there, spend the few minutes to do the "bt".
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.