public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Kereszt@crossys.com
To: pthreads-win32@sources.redhat.com
Subject: Re: pthread_exit() does not call the cleanups
Date: Fri, 12 Nov 2004 19:29:00 -0000	[thread overview]
Message-ID: <20041112192933.GF2444@cross> (raw)
In-Reply-To: <20041112170106.GE2444@cross>


My fault. False alarm.

At some point I failed to define __CLEANUP_CXX, and pthreadVSE doesn't work
fine with C++ exceptions enabled (VC++ compiler option: /GX or /EHsc). MSDN
says it can be mixed.. mostly.. but.. Unfortunately, the latest pthread
release doesn't contain precompiled VCE binary.. I tried it from the
previous (2004-06-22) release. Finally, I successfully compiled a fresh one
with VS7. I am simply unable to get work nmake, some PATH or whatever seems
to be missing but I cant hunt forever. I'm from UNIX.. it looks much cleaner
for me..

Conclusion: Now, it works.. Maybe, this will help others browsing mail
archives :)

Thanks and best regards,
Laszlo


> Sorry.. here it is.
> Thanks
> 
> > Well, but the attachment is missing...
> > 
> > Regards
> > Peter Slacik
> > 
> > Kereszt@crossys.com wrote:
> > 
> > >Hello,
> > >
> > >I've found that with pthread-win32 the pthread_exit() does not call the
> > >previously pushed (pthread_cleanup_push()) cleanup routines. I've just 
> > >tried
> > >it on a linux box and it works as documented (does the call).
> > >
> > >I'm a bit newbie to pthread so it might be my fault. I've attached a little
> > >sample code which reproduces the problem.
> > >
> > >Please, tell me what's the deal!
> > >
> > >Thanks,
> > >Laszlo

      reply	other threads:[~2004-11-12 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 16:51 Kereszt
     [not found] ` <4194EB9F.6050002@tatramed.sk>
2004-11-12 17:01   ` Kereszt
2004-11-12 19:29     ` Kereszt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041112192933.GF2444@cross \
    --to=kereszt@crossys.com \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).