This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Program exited with code 0303000 - SOLVED
- From: "Dan Osborne" <dan dot osborne at ramesys dot com>
- To: <cygwin at cygwin dot com>
- Date: Mon, 18 Oct 2004 14:57:59 +0100
- Subject: RE: Program exited with code 0303000 - SOLVED
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/