From: "Rob Fanner" <rfanner@stonethree.com>
To: <pthreads-win32@sources.redhat.com>
Subject: semaphores
Date: Thu, 30 May 2002 07:11:00 -0000 [thread overview]
Message-ID: <00c301c207e3$bb64ef00$0c01a8c0@thor> (raw)
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
I'm new to using pthreads-win32 (SNAPSHOT 2002-03-02), and I have to port
a program from Linux to Windows 2000. A bug has somehow crept into my
code, and I've narrowed the problem area down to a code fragment similar
to the following:
#include <semaphore.h>
#include <cassert>
#include <iostream>
using namespace std;
int main()
{
/**
* We want to check wether a semaphore can be initialised
* with a value.
*/
// a semaphore
sem_t psem;
// initialise it with value 10
assert(sem_init(&psem,0,10) == 0); // ASSERT NO 1
// if the semaphore initialisation was ok, the sem
// should now have the value 10
int ret = 0;
assert(sem_getvalue(&psem,&ret) == 0); // ASSERT NO 2
// if no errors occured then value is now in the
// integer ret
cout << endl << "sem_getvalue() returns value " << ret << endl << flush;
return 0;
}
I'm using MS VC++ 6.0, and I'm linking with the precompiled pthreadVCE.lib library.
At runtime, the first assert() passes OK, but second fails.
I have no idea why this fails (hopefully it's simply a newby error, and not a bug in
the pthreads-win32 lib), but it does.
Thanks
Rob
[-- Attachment #2: Type: text/html, Size: 2813 bytes --]
next reply other threads:[~2002-05-30 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 7:11 Rob Fanner [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 4:25 Semaphores Platzer Wolfgang
2002-05-30 8:49 semaphores Nicolas EDEL
2002-05-30 7:49 semaphores Bossom, John
2002-05-30 8:37 ` semaphores Phil Frisbie, Jr.
2002-05-30 9:33 ` semaphores Rob Fanner
2002-05-30 9:38 ` semaphores Rob Fanner
2002-05-30 22:32 ` semaphores Ross Johnson
2002-05-31 0:48 ` semaphores Rob Fanner
2002-06-02 21:35 ` semaphores Ross Johnson
1999-04-20 13:08 semaphores Michael Ambrus
1999-04-20 19:16 ` semaphores Ross Johnson
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='00c301c207e3$bb64ef00$0c01a8c0@thor' \
--to=rfanner@stonethree.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).