Problem Report Number |
0043 |
Submitter's Classification |
Test Suite problem |
State |
Resolved |
Resolution |
Test Suite Deficiency (TSD) |
Problem Resolution ID |
TSD.PX.0018 |
Raised |
2006-10-14 05:12 |
Updated |
2006-10-17 15:01 |
Published |
2006-10-17 15:01 |
Product Standard |
PSE52 Realtime Controller 1003.1-2003 System |
Certification Program |
POSIX Certified by IEEE and The Open Group |
Test Suite |
VSTH-PSE version 5.4.5 |
Test Identification |
PTHR.os/mutexattr_rt/pthread_mutexattr_setprotocol/T.pthread_mutexattr_
setprotocol 11 |
Problem Summary |
Some test cases use wrapper functions that may alter the expected
behavior and result in test failures. |
Problem Text |
Many of the pthread test cases use various wrapper functions instead
of the pthread API, for instance vsth_pthread_create(),
vsth_pthread_join(), vsth_sched_yield(), etc. These wrapper functions
may disturb the scheduling of threads which no longer have the
expected behavior (expected by the test code that is).
The wrapper function vsth_pthread_create() does a blocking operation
when it communicates with the host system. This disturb the test since
the wrapper does not have the same scheduling characteristics as the
function it encapsulates (here, pthread_create()) and results in the
failure of the test case indicated below.
|
Test Output |
***********************************************************************
/tset/PTHR.os/mutexattr_rt/pthread_mutexattr_setprotocol/T.pthr
ead_mutexattr_setprotocol 11 Failed
Test Description:
If the _POSIX_THREAD_PRIO_PROTECT option is supported:
when a thread unlocks a mutex that has been initialized with
the
PTHREAD_PRIO_PROTECT protocol attributes,
then it shall not be subject to being moved to the tail of the
scheduling
queue at its priority.
Posix Ref: Component PTHREAD_MUTEXATTR_SETPROTOCOL Assertion
9945-1:1996 13.6.1.2-11(C)
Test Information:
Thread 2 exitval, expected 0, got 2
|