I configured and built with linux-220.127.116.11 and xenomai-jki for-upstream
snapshot: f98569c8eec5df605f806ff58e789668720805ee. I noticed that you removed
the PTHREAD_WARNSW so I removed the call to pthread_set_mode_np to remove the
PosixThread/PosixThread.cpp:1607: error: 'PTHREAD_WARNSW' was not declared in
PosixThread/PosixThread.cpp:1607: error: 'pthread_set_mode_np' was not declared
in this scope
I am able to run all of my user space application code and unit test code which
uses CanFestival open source CAN library. I am also able to run the xeno-test
which runs to completion with no errors. When I run the mutex-torture tests I
still get the following errors which I have not looked into in more detail yet:
FAILURE: timed_waiter, waited 4.110 us
FAILURE: timed_mutex mutex_destroy: 22 (Invalid argument)
I am now looking at xenomai-rpm branch which one is close to 2.5.2 release?
From: Gilles Chanteperdrix [mailto:gilles.chanteperd...@xenomai.org]
Sent: Friday, March 05, 2010 1:37 PM
To: Charlton, John
Cc: 'jan.kis...@web.de'; xenomai-core
Subject: Re: [pull request] Fixes and workarounds for the cond issues
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:
You are probably missng the changes for recursive_cond_wait for the posix skin
which were commited in the development branch. You do not see it because the
new mutex-torture tests were added before the recursive cond test.
> r...@mcs2:/usr/xenomai/bin# ./mutex-torture-native simple_wait
> recursive_wait timed_mutex
> FAILURE: timed_waiter, waited 3.870 us r...@mcs2:/usr/xenomai/bin#
> ./mutex-torture-posix simple_wait recursive_wait errorcheck_wait
> 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?
This kind of thing is exactly the reason why I told I would work quietly on
this issue. Things will be ready on monday, but it would help us a great deal
if you could test the development branch on monday, at the same time as when we
are validating it on our test platforms.
Can not do better right now.
Xenomai-core mailing list