JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
Locks are released out of order. The preferred order of release is the opposite of the order in which the locks were acquired: newer locks should be released before older ones.
Releasing locks out of order can lead to priority inversion on some systems.
| Class Name | Lock/Unlock Mismatch | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Significance | style | |||||||||
| Mnemonic | CONCURRENCY.LOCK.MISMATCH | |||||||||
| Categories |
|
|||||||||
| Availability | Available for C and C++. |
|||||||||
| Enabling | Checks for this warning class are
disabled by default. To enable them, add the following WARNING_FILTER
rule to the project configuration file.
WARNING_FILTER += allow class="Lock/Unlock Mismatch" |
Lock/Unlock Mismatch warnings can be triggered by the following functions.
Japanese (ja)
#include <pthread.h>
pthread_mutex_t L1;
pthread_mutex_t L2;
void mismatched_locks(){
pthread_mutex_lock(&L1);
pthread_mutex_lock(&L2);
/* ... operate on locked data */
pthread_mutex_unlock(&L1); /* 'Lock/Unlock Mismatch' warning issued here */
pthread_mutex_unlock(&L2); /* 'Lock/Unlock Mismatch' warning issued here */
}
The following configuration file parameters affect checks for this warning class.