From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24424 invoked by alias); 25 Feb 2003 17:26:31 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 24412 invoked from network); 25 Feb 2003 17:26:31 -0000 Received: from unknown (HELO calypsoo.voxware.com) (63.167.41.125) by 172.16.49.205 with SMTP; 25 Feb 2003 17:26:31 -0000 Received: from zetar (12-253-95-100.client.attbi.com [12.253.95.100]) by calypsoo.voxware.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id FTC8ZSWZ; Tue, 25 Feb 2003 12:26:30 -0500 Subject: Trouble with mutex/cond destroy on WINCE 3.0 From: "Craig A. Vanderborgh" To: pthreads-win32@sources.redhat.com Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 25 Feb 2003 17:26:00 -0000 Message-Id: <1046194147.4455.22.camel@zetar> Mime-Version: 1.0 X-SW-Source: 2003/txt/msg00025.txt.bz2 Hello All: I have just done a port of pthreads-win32 to our recently completed arm-wince-pe GNU development environment. This is different that what others have been doing with pthreads-win32 in the following ways: 1. We are not using Visual C++ or EVC. We have our own port of the GNU toolchain (binutils-2.13.90 & gcc-3.2). 2. Except for a very few primitives from coredll.dll, we are not using the Micro$oft runtime - we are using "newlib" instead. The porting work that was required seemed fairly straightforward and affected mostly only header files in the end. Unfortunately, the result is not entirely working yet. In particular, mutex/condvar destruction is always returning "16" instead of "0" (EBUSY??). Here is an example program that shows the problem, along with the output: #include #include main(int argc, char *argv[]) { int i, stat; pthread_mutex_t mutex; pthread_cond_t cond; pthread_win32_process_attach_np(); pthread_win32_thread_attach_np(); stat = pthread_mutex_init(&mutex, NULL); printf("pthread_mutex_init returns %d, errno %d\n", stat, errno); stat = pthread_cond_init(&cond, NULL); printf("pthread_cond_init returns %d, errno %d\n", stat, errno); stat = pthread_cond_destroy(&cond); printf("pthread_cond_destroy returns %d, errno %d\n", stat, errno); stat = pthread_mutex_destroy(&mutex); printf("pthread_mutex_destroy returns %d, errno %d\n", stat, errno); getchar(); } The output is thus: thread_mutex_init returns 0, errno 0 pthread_cond_init returns 0, errno 0 pthread_cond_destroy returns 16, errno 0 pthread_mutex_destroy returns 16, errno 0 Apparently "EBUSY" is returned when there are waiters on synchronization objects. Clearly that can't be the case here so there must be something wrong with my port. The question is - what?? Any ideas on where to look or what to do would be vastly appreciated. TIA, craig vanderborgh voxware incorporated