From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18890 invoked by alias); 15 May 2002 14:50:30 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 18882 invoked from network); 15 May 2002 14:50:28 -0000 Received: from unknown (HELO mail.bossmedia.se) (212.247.84.108) by sources.redhat.com with SMTP; 15 May 2002 14:50:28 -0000 Received: from nilhen1 (not verified[212.247.84.85]) by mail.bossmedia.se with MailMarshal (4,2,5,0) id ; Wed, 15 May 2002 16:54:05 +0200 Reply-To: From: "Henrik Nilsson \(Developer\)" To: Subject: RE: Exceptions and so Date: Wed, 15 May 2002 07:50:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal In-Reply-To: X-SW-Source: 2002-05/txt/msg00146.txt.bz2 Hi Well it's really simple code inside the shared object. Not even this is working prinf("Throw") try{ throw 1; } catch(int i){ prinf("Catch") } I got the same result when compiling with gcc or g++ Bjorn Can you specify comp.lang.c++.moderated Thanks! /Henrik >Hi Henrik, > You should be able to throw exceptions in a shared object >and even accross the so interface, but you have to be very >carefull. I have had interesting results stemming from >premature unloading of libraries due to thrown exceptions. >A simple design flaw on my behalf due to insufficient >understanding, but quite educational i guess;) > You might want to check out comp.lang.c++.moderated, since there is an interesting thread running now about the binary compatibility of shared objects. Perhaps you could try to post a small contained example demonstrating the problem? Yours sincerely, bjorn