From: "Bossom, John" <John.Bossom@Cognos.COM>
To: "Romano Paolo Tenca" <rotenca@telvia.it>,
"Pthreads-Win32 list" <pthreads-win32@sources.redhat.com>
Subject: RE: problem in pthread.h
Date: Mon, 05 Jun 2006 18:12:00 -0000 [thread overview]
Message-ID: <4ABB890A1781774888DB6505E6F0E3B36E9606@sottemail2.ent.ad.cognos.com> (raw)
The pthread_cleanup_push defines a scoped block that is completed by the
pop macro.
This scoping is necessary in order that the internal local variable,
_cleanup, still exists at when the pop is actually called. The pop
expects the values in the _cleanup to still be available.
-----Original Message-----
From: pthreads-win32-owner@sourceware.org
[mailto:pthreads-win32-owner@sourceware.org] On Behalf Of Romano Paolo
Tenca
Sent: Monday, June 05, 2006 2:06 PM
To: Pthreads-Win32 list
Subject: problem in pthread.h
In pthread.h 2.7.0 line 762 i find:
#define pthread_cleanup_push( _rout, _arg ) \
{ \
ptw32_cleanup_t _cleanup; \
\
ptw32_push_cleanup( &_cleanup, (ptw32_cleanup_callback_t)
(_rout), (_arg) ); \
#define pthread_cleanup_pop( _execute ) \
(void) ptw32_pop_cleanup( _execute ); \
}
It seems to me that it must be:
#define pthread_cleanup_push( _rout, _arg ) \
{ \
ptw32_cleanup_t _cleanup; \
ptw32_push_cleanup( &_cleanup, (ptw32_cleanup_callback_t)
(_rout), (_arg) ); \
}
#define pthread_cleanup_pop( _execute ) \
(void) ptw32_pop_cleanup( _execute );
--
Romano Paolo Tenca
This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
next reply other threads:[~2006-06-05 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 18:12 Bossom, John [this message]
2006-06-05 19:08 ` Romano Paolo Tenca
2006-06-05 19:16 ` Romano Paolo Tenca
-- strict thread matches above, loose matches on Subject: below --
2006-06-05 19:17 Bossom, John
2006-06-05 18:05 Romano Paolo Tenca
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=4ABB890A1781774888DB6505E6F0E3B36E9606@sottemail2.ent.ad.cognos.com \
--to=john.bossom@cognos.com \
--cc=pthreads-win32@sources.redhat.com \
--cc=rotenca@telvia.it \
/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).