aCC runtime error

[twang]

Hi all,
Recently we run into problem with our SCM on our appl server which is a "ia64 hp server rx5670", the SCM process crashed with SIGABRT when we run a large case (it should use more memory storage), and the following error occurs -

08/10/13 00:47:35: Starting 1st scheduling (non-shared resource and material constrained)

1:250905599.999590009451,0.000000000000

aCC runtime: Uncaught exception of type "std::bad_alloc".

we got this error for std::bad_alloc class, and seems that NOT all virtual functions are correctly defined in the derived classes or HP-UX does not support thread-safe. The following link shows some info about thread-safe implementations on HP-UX…

http://www.boost.org/doc/libs/1_34_0/doc/html/thread.html

Should you have any idea what the problem could be or whether there is any known patch for aCC runtime library for this problem, please advise.
Many thanks.

[Dennis Handly · Accepted solution]

Everything you need to know is in my message and the Standard.

>we got this error for std::bad_alloc class,

bad_alloc means you are out of memory on operator new or operator new[]. It has nothing to do with virtual functions nor threading. These have their own messages.

You will have to increase maxdsiz/maxdsiz_64bit or possibly add more swapspace.

[jodymckinzie]

I am getting this error:

Running al_engine command...

aCC runtime: Uncaught exception of type "std::basic_string<char,std::char_traits<char>,std::allocator<char> >".

sh: 15205 Abort(coredump).

I added oracel to the bodi group in the /etc/group and made sure that bodi was the group associated with /local/apps/bods3 (The bods3 home directory).

This seemed to resolve my problems...just posting it here for anyone who may be having these problems.

[Dennis Handly]

>just posting it here for anyone who may be having these problems.

This is a completely different error and has nothing to do with the original topic.

[Samadi]

Hi,

I am getting the following error message:

aCC runtime: Uncaught exception of type "std::runtime_error".

Do anyone have any idea on this?
What could be the problem and how this can be resolved.

I am using HP-UX ia64 11.23.

Thanks

[Dennis Handly]

>What could be the problem and how this can be resolved?

You need to get a stacktrace so you can see where it is being thrown.

What is your libCsup version?  Newer version may print out what() with more details.