|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2093 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 2093.
Report 2093 Actions
Problem Report Number 2093 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1064 Raised 1970-01-01 08:00 Updated 2003-03-13 08:00 Published null Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98) Certification Program The Open Brand certification program Test Suite VSTH version 5.2.1 Test Identification PTHR.os/condattr/pthread_condattr_setpshared 3 Problem Summary TSD5TH.00084 The test receives a SIGABRT when it attempts to unlock a mutex it has not locked. The stack trace from the core file generated: vsth_sp_clear+0x58(ff320000, 0, 0, 0, 0, ff320018) vsth_sp_init+0x260(ff... Problem Text
The test receives a SIGABRT when it attempts to unlock a mutex
it has not locked.
The stack trace from the core file generated:
vsth_sp_clear+0x58(ff320000, 0, 0, 0, 0, ff320018)
vsth_sp_init+0x260(ff320000, ff1f57e8, 3, 80000001, 5, 0)
t3_f1+0x188(414e0, 41f28, 444ef, 445e0, 444ee, 3e6ea)
test3+0xa4(0, 1, 3, 0, ffbef642, 3e544)
tet_invoketp+0x5c(3, 0, 3, 1, 41348, 3aba0)
call_1tp+0x29c(3, 1, 3, 0, 3, 3aba0)
call_tps+0x98(3, 1, 0, 0, 1, 3abc0)
tet_tcm_main+0x498(1, ffbefac4, 0, 1f978, 21338, ffbefc36)
main+0x68(1, ffbefac4, ffbefacc, 3a800, 0, 0)
_start+0xb8(0, 0, 0, 0, 0, 0)
The function test3() prints out what the test is testing, and calls
t3_f1(). That function gets the scheduling priorities, mmaps
a sync point, and calls vsth_sp_init to initialize it. The
function vsth_sp_init() creates a condattr object, a mutexattr
object, a condition variable, and a mutex. It sets the protocols for
the condition variable and mutex and initializes them, then calls
vsth_sp_clear(). That function calls pthread_mutex_unlock():
int
vsth_sp_clear( VSTH_PSP psp )
{
int rval;
pthread_t mytid;
if ( Vsth_debug )
{
mytid = pthread_self();
tet_printf("%d vsth_sp_clear enter:", (int) mytid);
}
rval = 1;
if ( psp )
{
( void ) pthread_mutex_unlock( &psp->m );
psp->p = 0L;
rval = 0;
}
if ( Vsth_debug )
{
tet_printf("%d vsth_sp_clear exit: %d", (int) mytid, rval);
}
return(rval);
}
However, none of the preceeding functions has called
pthread_mutex_lock().
>From the description of pthread_mutex_unlock() in System Interfaces
and Header, Issue 5:
"If a thread attempts to unlock a mutex that it has not locked or a
mutex which is unlocked, undefined behavior results."Test Output
************************************************************************
****************************************
/tset/PTHR.os/condattr/pthread_condattr_setpshared/T.pthread_condattr_se
tpshared 3 UNREPORTED
Test Information:
If the symbol _POSIX_THREAD_PROCESS_SHARED is defined:
a condition variable initialized with a condition variable attributes
object whose process-shared attribute has been initialized by a call
to pthread_condattr_setpshared(attr, PTHREAD_PROCESS_SHARED) may be
operated upon by any thread with access to the memory in which the
condition variable is allocated.
Posix Ref: Component PTHREAD_CONDATTR_SETPSHARED
Assertion 9945-1:1996 11.4.1.2-3(C)
************************************************************************
****************************************Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
A test suite deficiency is recommended
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion
This is an agreed Test Suite Deficiency.
Problem Reporting System Options:
- View Report 2093
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority