Operating System - HP-UX
1832759 Members
2974 Online
110045 Solutions
New Discussion

Re: core dumped before reaching main()

 
Sivakrishna
New Member

core dumped before reaching main()

Hi,

The following is the trace o/p of the core dumped by our executable.

(gdb) bt
#0 0xc020b748 in kill+0x10 () from /usr/lib/libc.2
#1 0xc01a6624 in raise+0x24 () from /usr/lib/libc.2
#2 0xc01e6a18 in abort_C+0x160 () from /usr/lib/libc.2
#3 0xc01e6a74 in abort+0x1c () from /usr/lib/libc.2
#4 0xc2ee34f0 in std::terminate+0x38 () from /usr/lib/libCsup_v2.2
#5 0xc2ee39b8 in ThrowException+0x74 () from /usr/lib/libCsup_v2.2
#6 0xc2ee3f18 in __throw__FPvT1+0x14c () from /usr/lib/libCsup_v2.2
#7 0xc3800674 in std::ios_base::setf+0x7c () from /usr/lib/libstd_v2.2
#8 0xc3800118 in std::ios_base::Init::Init+0x1e40 () from /usr/lib/libstd_v2.2
#9 0xcc5832ec in std::__sinit_RWTraceOstreamClient_cpp+0x2c () from /opt/nokiaoss/pf3party/irp/lib/libtrace.sl
#10 0xc2ee574c in __shlInit+0x88 () from /usr/lib/libCsup_v2.2 #11 0xcc572488 in _shlInit+0x20 () from /opt/nokiaoss/pf3party/irp/lib/libtrace.sl
#12 0xc2ee5080 in __shlinit+0xac () from /usr/lib/libCsup_v2.2 #13 0xc2ee75dc in _main+0x194 () from /usr/lib/libCsup_v2.2

(core dumped)

The executable was linked along with -
Flags: -D_RWCONFIG=12d -DRW_THR_OS_VERSION_HPUX=0x1111
Libraries: -lrt -lnsl -lm -l:libtls.sl -l:libCsup_v2.sl -l:libstd_v2.sl -ltls -lrpcsoc -lrpcsvc -ltrace -lthrexcept -lsync -lpointer -lfunctor -lfunctor_list -litc -lthread

Does it mean any other libraries have to be linked? Will the order of linking matter anyway? What version of rogue wave libraries can be used with HP-UX B.11.11??

Thank you,
sivakrishna.
7 REPLIES 7
Vincent Abad
Advisor

Re: core dumped before reaching main()

hello sivakrishna,

Take a look at these information:
http://h21007.www2.hp.com/dspp/ml/showArchiveMessage/1,,24!03!07!0050,00.html

Using iostream library and stlv2 may impose you to build your executable with the ACC option "-mt" (multi thread option available since ACC 3.30) if you have dependencies with thread library.

Hope this help,

--Vincent
Sivakrishna
New Member

Re: core dumped before reaching main()

Hi Vincent,

We are using -mt option already. May be the problem is with something else.

Thank you,
Sivakrishna.
Steve Steel
Honored Contributor

Re: core dumped before reaching main()

Hi


If you get a dump then what is the output of

file core

Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
Sivakrishna
New Member

Re: core dumped before reaching main()

The following is the output.

% file core
core: core file from 'myEXE' - received SIGABRT
Steve Steel
Honored Contributor

Re: core dumped before reaching main()

Hi

Check your patch level

which compiler version

Do you have
PHSS_28880
s700_800 11.11 HP aC++ -AA runtime libraries (aCC A.03.50)


Do you use -mt to compile and link

Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
Sivakrishna
New Member

Re: core dumped before reaching main()

% /opt/aCC/bin/aCC -V
aCC: HP ANSI C++ B3910B A.03.39

Yeah, we are using -mt during compilation and linking.
Mike Stroyan
Honored Contributor

Re: core dumped before reaching main()

You can get that problem from inconsistent use of -AA mode. If you use -AA in any c++ code you must use it when compiling all c++ code and when linking. Your use of libCsup_v2.sl would indicate that you are trying to use -AA mode.

You shouldn't be explictly linking the program with "-l:libCsup_v2.sl -l:libstd_v2.sl". You should be linking with "aCC -AA", which will link in the correct c++ runtime libraries. Any c++ shared libraries that you create should be linked with "aCC -AA -b".