From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4B952690.1060009@domain.hid> Date: Mon, 08 Mar 2010 17:32:16 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4B8D9711.5090704@domain.hid> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [pull request] Fixes and workarounds for the cond issues List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Charlton, John" Cc: "'jan.kiszka@domain.hid'" , xenomai-core Charlton, John wrote: > I merged some changes from git://git.xenomai.org/xenomai-jki.git for-upstream to my xenomai-2.5.1 release distribution > to include the rt_cond_wait and pthread_cond_[timed]wait work > arounds. I also merged changes to the mutex_torture.c. Everything builds and most tests seem to pass but I get the following output from the mutex-torture tests: > > root@domain.hid# ./mutex-torture-native > simple_wait > recursive_wait > timed_mutex > FAILURE: timed_waiter, waited 3.870 us > root@domain.hid# ./mutex-torture-posix > simple_wait > recursive_wait > errorcheck_wait > timed_mutex > FAILURE: timed_mutex mutex_destroy: 22 (Invalid argument) > > Do you have suggestions on how to resolve these errors hopefully > without moving to the full development branch? Ok. I found and fixed this bug. It was a bug in the testcase. It would really help us, however, if you could pull the full development branch, and just give it a quick test to see if it fixes the current issue. It is our hope that this development branch is close to what 2.5.2 will be. -- Gilles.