This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: pthread_mutex_unlock when mutex is not locked


Rubц╘n Pц╘rez de Aranda Alonso <rperez@sidsa.es> writes:
> I think the mutex is appropiate for the explained scenario.
> 
> The standard says: "If the mutex type is PTHREAD_MUTEX_RECURSIVE, then
> the mutex maintains the concept of a lock count. When a thread
> successfully acquires a mutex for the first time, the lock count is
> set to one. Every time a thread relocks this mutex, the lock count is
> incremented by one. Each time the thread unlocks the mutex, the lock
> count is decremented by one. When the lock count reaches zero, the
> mutex becomes available for other threads to acquire. If a thread
> attempts to unlock a mutex that it has not locked or a mutex which is
> unlocked, an error will be returned."

1. Nowhere in your original post did you've mention you use POSIX mutexes. 

2. Nowhere in the POSIX documents you will find anything about DSRs, so
   semantics of calling mutex operations from DSRs aren't defined by
   POSIX.

-- 
Sergei.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]