Operating System - HP-UX
1848836 Members
8346 Online
104038 Solutions
New Discussion

Re: Core Dump while handling Exceptions even after using -mt and -AA option

 
Jaya Venkataramanappa
Occasional Contributor

Core Dump while handling Exceptions even after using -mt and -AA option

We have upgraded Roguewave database to Sourcepro Edition 7 and the only change in the application is INFORMIXACCLIB which changed from "libinf5215dnat.sl" to "libinf6115dnat.sl". We are compiling the application with -mt and -AA option.
When we run the application the core is dumped where we throw exception in the catch block...

The core details are as follows:

Program terminated with signal 6, Aborted.
#0 0xc020e5d8 in kill+0x10 () from /usr/lib/libc.2
(gdb) list
146 lnptadbsrv.C: No such file or directory.
(gdb) bt
#0 0xc020e5d8 in kill+0x10 () from /usr/lib/libc.2
#1 0xc01a71c4 in raise+0x24 () from /usr/lib/libc.2
#2 0xc01e9170 in abort_C+0x160 () from /usr/lib/libc.2
#3 0xc01e91cc in abort+0x1c () from /usr/lib/libc.2
#4 0xc02f3f48 in terminate+0x38 () from /usr/lib/libCsup.2
#5 0xc02f4400 in ThrowException+0x70 () from /usr/lib/libCsup.2
#6 0xc02f4960 in __throw__FPvT1+0x14c () from /usr/lib/libCsup.2

The compiler version we are using is:

aCC: HP ANSI C++ B3910B A.03.57

Can anyone please help me out on this?




1 REPLY 1
Dennis Handly
Acclaimed Contributor

Re: Core Dump while handling Exceptions even after using -mt and -AA option

>core is dumped where we throw exception in the catch block...

Your stack trace indicates you did a throw without a catch. You have to do a throw within or under control of the try block.

If it isn't this simple mistake, then it could be compiler, aC++ runtime or trap/unwind lib issues.