Mail Archives: djgpp-workers/1996/09/29/09:28:11
Date: | Sun, 29 Sep 1996 09:25:51 -0400
|
From: | dj (DJ Delorie)
|
Message-Id: | <199609291325.JAA18970@delorie.com>
|
To: | eliz AT is DOT elta DOT co DOT il
|
CC: | djgpp-workers AT delorie DOT com
|
In-reply-to: | <Pine.SUN.3.91.960929100249.20703G-100000@is> (message from Eli Zaretskii on Sun, 29 Sep 1996 10:10:52 +0200 (IST))
|
Subject: | Re: `abort' in nested programs
|
> I'm not sure about the best way to solve this. Would a call to
> `__djgpp_exception_toggle' inside `abort' be OK? It would be nice to
> call it inside `_exit', but that won't work since `exit' calls `_exit'.
> Is there a way to detect whether exceptions point to the handlers inside
> surrently executing program?
Thinks that *must* be cleaned up on program exit must be called in
_exit(), and *not* exit(). I think that call should be moved, not
copied, to _exit.
Note that I've seen user C++ programs call _exit directly to avoid
static object destructors.
- Raw text -