Jaya_Kumar_Satri
asked on
terminate called after throwing an instance of 'int' Aborted (core dumped)
Hi,
Our application during the load test is exiting with zero size core dump (though the ulimit -c is set to unlimited), with the message "terminate called after throwing an instance of 'int' Aborted (core dumped)" displayed on the terminal.
The application is written in C++ and runs on linux.
the output of uname -a of the machine on which our application is run is -
Linux version 2.6.9-42.ELsmp (bhcompile@hs20-bc1-1.buil d.redhat.c om) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-2)) #1 SMP Wed Jul 12 23:27:17 EDT 2006
Our application during the load test is exiting with zero size core dump (though the ulimit -c is set to unlimited), with the message "terminate called after throwing an instance of 'int' Aborted (core dumped)" displayed on the terminal.
The application is written in C++ and runs on linux.
the output of uname -a of the machine on which our application is run is -
Linux version 2.6.9-42.ELsmp (bhcompile@hs20-bc1-1.buil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It seems to be a C++ application, and an exception (with int value) is thrown.
terminate() can be called if a function declares to throw one set of exception types, but another one is thrown, like:
void func() throw (std::bad_alloc)
{ int v = 5; throw v; } // terminate() will be called
And the terminate() causes abort() call to be done, which causes a crash.
terminate() can be called if a function declares to throw one set of exception types, but another one is thrown, like:
void func() throw (std::bad_alloc)
{ int v = 5; throw v; } // terminate() will be called
And the terminate() causes abort() call to be done, which causes a crash.
If you have quotas enabled, check them too.