Difference in Template instantiation between HP-UX 11.11 and Itanium.

[Mangesh T]

Observing different way of template instantiation as follows
HP_UX 11.11
mmm::synchronous::once *mmm::container<:synchronous::once> >::find(mmm::syn
chronous::once *

HP_Itanium
mmm::container::find(T) [with T = mmm::synchronous::once *, IMPL = mmm::vdeque<:synchronous::once>]

One of the application server is using this shared library for thread synchronization.

We see the difference in template instantiation as mentioned above while application server startup and later causing a core-dump ahead as :

Exception Handling Failure (exceptionClass == kExceptionClass.asUint64):Calling terminate()

Tried to catch it through run time exception as mentioned in gdb frame, but it’s not the location where the actual core is taking place.

[Dennis Handly]

>Observing different way of template instantiation as follows

I'm not sure what you trying to say or ask. These are fragments of compiler messages. Questions like this would imply you have a compile time error message?
What two compiler versions are you using?

>Exception Handling Failure (exceptionClass == kExceptionClass.asUint64):Calling terminate()

This likely means you are mixing g++ and aC++. This isn't supported.

Can you provide a stack trace.

[Mangesh T]

Thanks for the reply.

There are two questions posted. One was about template instantiation and second one about kexception.

1) We are using aCC compiler. Shared library is being used for thread safe communication which is implemented using template classes and functions.
Differences mentioned in problem description are posted for runtime implementation of template function calls during the Itanium migration from old HP-UX 11.11 system.
There is no compile time error message generated

2) Stack trace is attached herewith.

[Dennis Handly]

>Differences mentioned in problem description

I see no real differences. These are only formatting differences of compiler messages.

>There is no compile time error message generated

Then where did you get these message fragments?

>2) Stack trace is attached herewith.

This just says the aC++ runtime aborted. I assume with the above error message?
What aC++ runtime version are you using? What version of libunwind are you using?
Have any threads been created yet?

[Dennis Handly]

If you aren't using g++, I suppose this could be an optimizer problem in ~synchronizer. What opt level are you using?
Do you know where the throw was and where it should be caught?