![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| High Level Programming Post questions about C, C++, Java, SQL, and other programming languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Exception Handling | bertpereira | Shell Programming and Scripting | 5 | 01-14-2009 09:28 PM |
| MMU exception | Puntino | Linux | 2 | 05-07-2008 12:35 PM |
| Help with RPC Exception | ejbrever | HP-UX | 2 | 08-24-2006 02:08 PM |
| RPC Exception - Help | ejbrever | UNIX for Advanced & Expert Users | 0 | 08-21-2006 12:56 PM |
| exception handling | RichardS | UNIX for Advanced & Expert Users | 1 | 06-16-2004 05:29 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Linux g++ 2.95.3 exception handling
Anybody happen to be familiar with any deficiencies with g++ 2.95.3 regarding exception handling, specifically in multi-threaded / multi-module (shared library) based applications?
I'm seeing behavior where thrown exceptions are not caught, but basically ignored causing the application to terminate, even thought the code is appropriately within try/catch blocks. I haven't been using any optimization flags to build, but I tried compiling with -O0 to be sure and that didn't change anything. Thanks in advance. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|