benn/lumiera_documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

remove some lock sections in thread two_acquire_test

Browse source 
After acquired, the caller 'owns' the thread handle and can inspect it,
the associated thread is defined to be waiting for a wakeup signal
(and then one shouldn't do unlocked access to the thread handle)
This commit is contained in:
Christian Thaeter 2010-01-30 03:30:08 +01:00
parent 4aa5380311
commit 74560cdd99
1 changed files with 4 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
tests/backend/test-threadpool.c
View file

@ -83,17 +83,11 @@ TEST ("two-thread-acquire")
"test purpose",
&NOBUG_FLAG(NOBUG_ON));
LUMIERA_CONDITION_SECTION(NOBUG_ON, &t1->signal)
{
ECHO("thread 1 state=%s", lumiera_threadstate_names[t1->state]);
CHECK(LUMIERA_THREADSTATE_IDLE == t1->state);
}
ECHO("thread 1 state=%s", lumiera_threadstate_names[t1->state]);
CHECK(LUMIERA_THREADSTATE_IDLE == t1->state);
LUMIERA_CONDITION_SECTION(NOBUG_ON, &t2->signal)
{
ECHO("thread 2 state=%s", lumiera_threadstate_names[t2->state]);
CHECK(LUMIERA_THREADSTATE_IDLE == t2->state);
}
ECHO("thread 2 state=%s", lumiera_threadstate_names[t2->state]);
CHECK(LUMIERA_THREADSTATE_IDLE == t2->state);
LUMIERA_CONDITION_SECTION(NOBUG_ON, &t1->signal)
{