Getting RethrowException on HPUX 11.23 IA64 from C/C++ code

[v2_1]

Hello experts,
Could anyone let me know if a good patch / uppgrade will resolve the exception?
Thanks,
-V2


# gdb32 ./mypg ../scripts/core.mypg

HP gdb 3.4 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00.

Copyright 1986 - 2001 Free Software Foundation, Inc.

Hewlett-Packard Wildebeest 3.4 (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.

..(no debugging symbols found)...

Core was generated by `mypg'.

(no debugging symbols found)...#0 0xc284e310 in U_is_readable+0x4 () from /usr/lib/libcl.2

(gdb) where

#0 0xc284e310 in U_is_readable+0x4 () from /usr/lib/libcl.2

#1 0xc284e0b4 in U_get_shLib_unw_tbl+0x34 () from /usr/lib/libcl.2

#2 0xc294dde0 in Get_func_info+0x94 () from /usr/lib/libCsup_v2.2

#3 0xc294e384 in TCompTechFunctionDescriptor::TCompTechFunctionDescriptor+0x54 () from /usr/lib/libCsup_v2.2

#4 0xc294e634 in CreatePCtoExceptionDescriptor+0x20 () from /usr/lib/libCsup_v2.2

#5 0xc294ecd0 in findCurrentException+0x84 () from /usr/lib/libCsup_v2.2

#6 0xc294f6e0 in RethrowException+0x70 () from /usr/lib/libCsup_v2.2

#7 0xc294fa28 in __rethrow+0x134 () from /usr/lib/libCsup_v2.2

#8 0xca22d11c in mypg::DataBroker::getTypeId+0x934 () from /opt/mypg/lib/libVxmypg.sl

#9 0xca1d7594 in mypg::HostMsgSampleIntInt::processSample+0xe4 () from /opt/mypg/lib/libVxmypg.sl

#10 0xca15f4d8 in mypg::Agent::handleTypedMessage+0x2ad8 () from /opt/mypg/lib/libVxmypg.sl

#11 0xca0f543c in mypg::Agent<:objectrequest>::handleMessage+0x64 ()

from /opt/mypg/lib/libVxmypg.sl

#12 0xca0ed37c in TypedMsgHandler<:agent>::MsgWrapper<:objectrequest>::forwardTo+0x34 ()

from /opt/mypg/lib/libVxmypg.sl

#13 0xca0e52d0 in MessageQueue<:agent>>::svc+0x2d0 ()

from /opt/mypg/lib/libVxmypg.sl

#14 0xc906a9c4 in ACE_Task_Base::svc_run+0x5c () from /opt/mypg/lib/libvxACE.sl.3

#15 0xc8fcee28 in ACE_Thread_Adapter::invoke_i+0xf0 () from /opt/mypg/lib/libvxACE.sl.3

#16 0xc8fcecd4 in ACE_Thread_Adapter::invoke+0xbc () from /opt/mypg/lib/libvxACE.sl.3

#17 0xc8f63d90 in ace_thread_adapter+0x38 () from /opt/mypg/lib/libvxACE.sl.3

#18 0xc2536024 in __pthread_bound_body+0xa8 () from /usr/lib/libpthread.1

#19 0xc2566ab4 in __pthread_bound_start+0x14 () from /usr/lib/libpthread.1

[Dennis Handly]

You neglected to mention you are running a PA executable on IPF. Also the PA version of gdb you have is old. You should get a newer version, PHSS_34417.

Was there a particular signal involved? It is impossible to fail on U_is_readable+0x4 unless you sent a INT or QUIT signal and it just happened to be at that one instruction.

I can only suggest you make sure you have the latest Aries and libcl patches: PHSS_35045 PHSS_33903

[Dennis Handly]

Hmm, from your original thread, you do have two of the patches I mentioned: PHSS_35045 PHSS_33903
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1092168

I suggest you get a better gdb and retry the stack trace.

[v2_1]

Increasing the stack size for the pthread i the C program resolved the issue.

All the symptoms otherwise lead to all absurd diagnosis.