You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2020/08/24 11:40:51 UTC

[GitHub] [mynewt-nimble] andrzej-kaczmarek commented on issue #824: L2CAP COC: nimble@mynewt crashes when flooding a channel

andrzej-kaczmarek commented on issue #824:
URL: https://github.com/apache/mynewt-nimble/issues/824#issuecomment-679076119


   > Confirmed: using os_sem solves this issue. Interesting system design to have the watchdog triggering for waiting mutexes but not for semaphores :-) Maybe that could be added to the doc pages?!
   
   that's not the problem with mutex itself. sample code acquires mutex in on task (flooder) and releases it in another (main). this means an attempt to release mutex always returns an error since task which tries to release mutex does not own it, while an attempt to acquire mutex will not block since mutexes are recursive so the same task can acquire a mutex more than once. so effectively sample code spins in `_send` which triggers watchdog.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org