Skip navigation.
 
mlRe: c++ exceptions causing abort
FROM : Benjohn
DATE : Mon Dec 13 19:53:24 2004

On 13 Dec 2004, at 16:40, John Stiles wrote:

> This isn't possible.


Oh blast. Thank you for confirming that.

> As a general rule of thumb, if you didn't compile it yourself, you
> probably can't throw through it.
> Try catching all throws at as low a level as possible without going
> back into AppKit, like this:
>
>     Our c++ code            - throw occurs here.
>     Our c++ code
>     Our c++ code             - try catching here
>     App Kit / Foundation
>     App Kit / Foundation
>     App Kit / Foundation
>     App Kit / Foundation
>     Our handler            
>     App Kit / Foundation
>     App Kit / Foundation
>     Root of the stack
>
> And then post some sort of notification so the run-loop can know
> what's going on.


*nods*

Can you see a nice way of achieving this, that avoids adding try catch
blocks in lots of places (I imagine there are many points where our
code is invoked by a caller that doesn't allow exceptions to pass
through it)? As an example, perhaps we could patch the objective c
message dispatcher to ensure calls to our code are wrapped in a try
catch block.

Cheers,
   Benjohn

Related mailsAuthorDate
mlc++ exceptions causing abort Benjohn Dec 13, 17:09
mlRe: c++ exceptions causing abort John Stiles Dec 13, 17:40
mlRe: c++ exceptions causing abort Michael Crawford Dec 13, 19:24
mlRe: c++ exceptions causing abort Michael Crawford Dec 13, 19:24
mlRe: c++ exceptions causing abort Benjohn Dec 13, 19:53
mlRe: c++ exceptions causing abort John Stiles Dec 13, 20:38
mlre: c++ exceptions causing abort Keith Ray Dec 13, 20:39
mlre: c++ exceptions causing abort Martin Dec 14, 01:29
mlRe: c++ exceptions causing abort Benjohn Dec 14, 14:34