This is the mail archive of the pthreads-win32@sources.redhat.com mailing list for the pthreas-win32 project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: mingw32 DLLs, threads and exceptions HOWTO

To: <rpj at ise dot canberra dot edu dot au>
Subject: Re: mingw32 DLLs, threads and exceptions HOWTO
From: "Thomas Pfaff" <tpfaff at gmx dot net>
Date: Mon, 11 Dec 2000 10:20:34 +0100
Cc: <pthreads-win32 at sources dot redhat dot com>
References: <002c01c06036$827a7da0$69856286@pcs.ditec.de> <3A338F13.69B85171@ise.canberra.edu.au>

Hello Ross,

catch(...) does not work simply because no exception is raised (LINUX won't
either). This is a MSVC runtime feature.

You have to install a SIGFPE signal handler and use setjmp/longjmp to get
FP exceptions.

Regards,
    Thomas

> Ross Johnson wrote
>
> As you noted, the exception1.c test fails. For some reason
> catch(...) isn't catching the deliberate zero divide exception.
> I've substituted a different exception, which passes. (The
> test simply confirms that the redefinition of catch in
> pthread.h works.)
>

References:
- mingw32 DLLs, threads and exceptions HOWTO
  - From: Thomas Pfaff
- Re: mingw32 DLLs, threads and exceptions HOWTO
  - From: Ross Johnson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]