![Blog of (former?) MySQL Entomologist: Dynamic Tracing of pthread_mutex_lock in MariaDB - First Steps Blog of (former?) MySQL Entomologist: Dynamic Tracing of pthread_mutex_lock in MariaDB - First Steps](https://1.bp.blogspot.com/-oAVakUAYbII/X2d6gkl39ZI/AAAAAAAAAiE/DZ4CpzMb2Kor3OMiEScXOH3OiFQBV3JuQCNcBGAsYHQ/s1196/pthread_mutex_lock_flame.png)
Blog of (former?) MySQL Entomologist: Dynamic Tracing of pthread_mutex_lock in MariaDB - First Steps
![Compiler/66AK2H12: pthread_mutex_lock(&critsec_) generates a do_AngelSWI - Code Composer Studio forum - Code Composer Studio™︎ - TI E2E support forums Compiler/66AK2H12: pthread_mutex_lock(&critsec_) generates a do_AngelSWI - Code Composer Studio forum - Code Composer Studio™︎ - TI E2E support forums](https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/81/Annotation-2020_2D00_07_2D00_28-171758.png)
Compiler/66AK2H12: pthread_mutex_lock(&critsec_) generates a do_AngelSWI - Code Composer Studio forum - Code Composer Studio™︎ - TI E2E support forums
![tihmstar on Twitter: "If you are like me strueggeling with: ../nptl/ pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Here is a workaround: sed -i 's/\.lock();/\.lock();usleep(100);/g' m2.cpp https://t.co ... tihmstar on Twitter: "If you are like me strueggeling with: ../nptl/ pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Here is a workaround: sed -i 's/\.lock();/\.lock();usleep(100);/g' m2.cpp https://t.co ...](https://pbs.twimg.com/media/EWXNwdvXYAAMw3t.png)
tihmstar on Twitter: "If you are like me strueggeling with: ../nptl/ pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Here is a workaround: sed -i 's/\.lock();/\.lock();usleep(100);/g' m2.cpp https://t.co ...
wrong use of pthread_mutex_lock(3) and pthread_mutex_unlock(3) in ec_threads.c · Issue #72 · Ettercap/ettercap · GitHub
Second pthread_mutex_lock() call returns ENOTRECOVERABLE instead of EDEADLK if atol() was called · Issue #181 · TritonDataCenter/illumos-joyent · GitHub
![SOLVED: Q4.9: If a program uses more than one mutex, and the mutexes can be acquired in different orders,the program can deadlock.That is,threads may block forever waiting to acquire one of the SOLVED: Q4.9: If a program uses more than one mutex, and the mutexes can be acquired in different orders,the program can deadlock.That is,threads may block forever waiting to acquire one of the](https://cdn.numerade.com/ask_images/a2b0e15b02684cf299bcac1522b90987.jpg)