This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] C++ vs forced unwinding
- From: Richard Henderson <rth at redhat dot com>
- To: Jan Vroonhof <jan dot vroonhof at insignia dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 4 Apr 2003 10:55:53 -0800
- Subject: Re: [RFC] C++ vs forced unwinding
- References: <20030401021229.GA6277@twiddle.net> <wvlistxaol7.fsf@prospero.boston.redhat.com> <20030401134858.A1484@twiddle.net> <20030402095654.7e60fd64.bkoz@redhat.com> <20030402085254.A3198@twiddle.net> <g3fzp023oi.fsf@bart.isltd.insignia.com>
On Wed, Apr 02, 2003 at 06:46:05PM +0100, Jan Vroonhof wrote:
> e.g., I presume C app, C library and no threads works always (apart
> from debugging stripped binaries with -fomit-frame-pointer). At which
> point do things start going wrong?
C++ app linked to C library not using -fexceptions, results in
5. Runs but pthread_cancel silently does not execute C++ destructors
r~