[En-Nut-Discussion] Feature Request 1572837: mutex API nesting level info

[Matthias Ringwald]

I've posted in the tracker to ask what it is used/needed for.  
Otherwise I would agree with Nathan that it's probably for debugging  
purposes.

Hi

adding the return statement would not be hard. But why do you want  
this? I assume it could be used to write some asserts.
Would directly accessing mutex->count be very inconvenient in your case?

matthias


On 09.07.2008, at 16:31, Nathan Moore wrote:

> I believe that what you would actually get back is how many times the
> current thread has called NutMutexLock on a particular lock.
> The nesting of these mutexes is so that if a function like fputc  
> were to
> lock the file's mutex around it's operation, and then fputc was also  
> called
> by fprintf which needed to keep all of it's output together it could  
> also
> lock the file's mutex without worrying about blocking fputc being  
> blocked or
> releasing the lock prematurely.
> Returning the count might offer some debugging help (ie  
> "NutMutexUnlock just
> returned != 0 at what should have been top level"), but I don't see  
> how
> useful it would be in production use.
>
> Nathan
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion