🚀 go-pugleaf

I haven't had a chance to look at your specific example, but yes,
there are some exception handling bugs in the 3.70 version of the HP
C++ compiler which do involve objects being destroyed twice in some
cases.

I'm told by the HP people that there are actually a few separate
exception handling bugs which all show the same basic symptoms (i.e.
objects being destroyed twice). Many have been fixed and these fixes
are included in the latest patches which are already available. You
may want to try installing those. Others (like the one we ran into)
are not fixed by those patches, but are fixed in a patch which I'm
told should be available within the next week.

			Ethan Shayne
			eshayne@ibm.net


Michael Bresnahan <mbresnahan1@mmm.com> wrote:

>This simple program illustrates what looks like a bug in the exception handling
>stack unwinding code of HP's CC/libCC or there is something about C++ I don't
>understand.  It shows the same object being destructed twice, and one object
>left hanging.  I am using:

>CC:	HP C++ HPCPLUSPLUS  A.03.70
>libC:	HP C++ HPCPLUSPLUS  A.03.70
>OS:	HP-UX devux01 A.09.04 B 9000/891 342319241 16-user license