SIGSEGV in exception destruction

Hi All,

I'm facing a same problem which was reported earlier in this forum

http://forum.sun.com/jive/thread.jspa?forumID=305&threadID=71170

Running on the machine SunOS hkxp0414 5.9 Generic_118558-11.

However I'm not able to get in which patch this problem is fixed, any pointer will be of great help.

Thanks

Saurabh

[365 byte] By [SaurabhJain] at [2007-11-26 7:49:59]
# 1

Fortunately, the answer is easy. :-)

Get the current set of patches. You do not need to try to locate old patches that have been superceded. Current patches always include every fix that was included in earlier patches.

You can find all current patches for Sun Studio and also the current Solaris patches needed for Sun Studio here:

http://developers.sun.com/prodtech/cc/downloads/patches/index.jsp

It is best to get all the patches for the components you use.

clamage45 at 2007-7-6 20:07:14 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 2

Hi,

Thanks for your reply, the patch text suggests that SEGV will happend only deque is used. Is this true or we can get similar kind of crash in other exception handling as well.

6339010 SEGV during destruction of exception object containing a deque

6326163 C++ exception propagates outside of destructor, while "stack unwinding"

Here is the portion of back trace which we are getting,

fe405094 __1cIOvXplRefHMTRef_t2I6M_l_ (fdb6ae88, 23ec, fe529e2c, 15234, fe5263b4, fdb6ef28)

ff2531d8 __1cUOvPollingApplicationPPAParamNotFound2T6M_v_ (fdb6ae88, fdb6ae40, 0, 1, fdb6ae40, ff2531a8) + 30

fdb5433c __1cH__CimplHex_free6F_v_ (fdb6ef2c, 1, fdb6ae40, 16260, fdb6a538, fdb6ef2c) + 68

PAParamNotFound object is created when an exception is caught to log error messages.

Would like to know if this crash can be because of same reason.

Thanks

Saurabh

SaurabhJain at 2007-7-6 20:07:14 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 3

Any number of things can cause a SEGV, including errors in yoru program.

If the crash occurs in __1cH__CimplHex_free6F_v_ == void __Cimpl::ex_free()

it is probably a bug in the C++ exception handling. At least two bugs are already fixed in C++ runtime library patches (Solaris SUNWlibC patch).

One additional bug was recently fixed, and will appear in the next C++ runtime library patch. That bug shows up only in massively multi-threaded programs.

clamage45 at 2007-7-6 20:07:14 > top of Java-index,Development Tools,Solaris and Linux Development Tools...