This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: eCos and C++ exceptions
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- Cc: eCos Discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 21 Sep 2005 21:51:10 +0200
- Subject: Re: [ECOS] eCos and C++ exceptions
- References: <NEBBKHCFDGIGIJEHDJFCGEOAAKAB.pderocco@ix.netcom.com>
On Wed, Sep 21, 2005 at 12:38:50PM -0700, Paul D. DeRocco wrote:
> I'm using the arm-elf toolchain, which has a reasonably efficient SJLJ
> implementation for C++ exceptions (as long as exception specification
> checking is turned off). Does the eCos thread structure support this form of
> exception handling?
>
> C++ is a pretty crippled language if you can't at least rely upon bad_alloc
> as a way of aborting constructors. In particular, you can't use any of the
> standard container classes, or strings.
>
> I understand that nothing in eCos is intended to throw exceptions, or be
> safe in the presence of exceptions thrown by application code, but I can
> deal with that, as long as the eCos gives each thread its own exception
> context chain.
>
> If eCos doesn't provide this support, has anyone thought about what it would
> take to add it?
eCosCentric have implemented full C++ exception support in their eCosPro
product.
There has also been some efforts by Oyvind Harboe. See the email
archives.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss