This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Re: problems with pthreads && c++ (suspect wait conditions)
- From: "Conrad Scott" <Conrad dot Scott at dsl dot pipex dot com>
- To: <cygwin at cygwin dot com>
- Date: Fri, 5 Jul 2002 18:28:26 +0100
- Subject: Re: Re: problems with pthreads && c++ (suspect wait conditions)
- References: <200207051859.43753.maksik@gmx.co.uk>
"Max Zaitsev" <maksik@gmx.co.uk> wrote:
> It would be nice if somebody at cygwin would document
> such a behavior of gcc, that is even if one don't have
> any try-catch blocks one still have to use
> -fno-exceptions to forbid them completeli kind of...
Another thing that I only realised recently, is that the new and
delete operators are not thread-safe in the current cygwin / gcc
world. You have to push things pretty hard to trip over it, but
there is a problem there. For what I'm working on (cygserver), I
ripped out all the new/deletes and used malloc/free with placement
new and explicit destructor calls. Ugly but it works (not that
that's a recommedation).
Earnie Boyd suggested -D__USE_MALLOC, as discussed recently on the
mingw-users list, but I've not got around to investigating that as
yet.
HTH,
// Conrad
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/