Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: "Dan Osborne" <dan DOT osborne AT ramesys DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Program exited with code 0303000 - SOLVED
Date: Mon, 18 Oct 2004 14:57:59 +0100
Message-ID: <MLECJOCAOOEMHIHMOACLGEFBCDAA.dan.osborne@ramesys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <MLECJOCAOOEMHIHMOACLGEJECCAA.dan.osborne@ramesys.com>
X-Ramesys-Professional-Services-MailScanner-Information: Please contact the ISP for more information
X-Ramesys-Professional-Services-MailScanner: Found to be clean
X-Ramesys-Professional-Services-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-3.4, required 5, IN_REP_TO -3.38)
Note-from-DJ: This may be spam

Dan Osborne wrote:
> OK, my voyage of discovery continues. I've added exception
> specifications to the appropriate functions (declarations and
> definitions - took a while to work out I needed it on both) but no
> change in behaviour.
>
> I've also remembered why I started to look at dumper.exe - If I don't
> run the prog in gdb then instead of "Program exited with code
> 0303000" I get ...
>
> Aborted (core dumped)
>
> Presumably because of the uncaught exception, despite a catch (...)
> in my main.

Ahem, the catch (...) wasn't being invoked because an exception was being
thrown that wasn't in the throw specification.

Removing the function throw specs solves the problem.

Dan
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.768 / Virus Database: 515 - Release Date: 22/09/2004


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/