La traduzione di questa pagina non è aggiornata. Fai clic qui per vedere l'ultima versione in inglese.

Difetti di concorrenza

Difetti relativi al codice multitasking

Questi checker rilevano problemi relativi al codice multitasking, come la corsa ai dati in cui più attività operano su una variabile non protetta o difetti di blocco in cui sezioni critiche sono coinvolte in uno stallo. Polyspace può rilevare i thread e le sezioni critiche nel codice oppure è possibile definirli manualmente nella configurazione di Polyspace.

Risultati di Polyspace

espandi tutto

Data raceMultiple tasks perform unprotected nonatomic operations on shared variable
Data race on adjacent bit fieldsMultiple threads perform unprotected operations on adjacent bit fields of a shared data structure
Data race through standard library function callMultiple tasks make unprotected calls to thread-unsafe standard library function
Blocking operation while holding lockTask performs lengthy operation while holding a lock
DeadlockCall sequence to lock functions cause two tasks to block each other
Destruction of locked mutexTask tries to destroy a mutex in the locked state
Double lockLock function is called twice in a task without an intermediate call to unlock function
Double unlockUnlock function is called twice in a task without an intermediate call to lock function
Missing lockUnlock function without lock function
Missing unlockLock function without unlock function
Multiple mutexes used with same condition variableThreads using different mutexes when concurrently waiting on the same condition variable is undefined behavior
Asynchronously cancellable threadCalling thread might be canceled in an unsafe state
Join or detach of a joined or detached threadThread that was previously joined or detached is joined or detached again
Missing or double initialization of thread attributeDuplicated initialization of thread attributes or noninitialized thread attribute used in functions that expect initialized attributes
Multiple threads waiting on same condition variableUsing cnd_signal or std::condition_variable::notify_one() to notify one of the threads waiting for the same condition variable might result in indefinite blocking
Signal call in multithreaded programProgram with multiple threads uses signal function
Use of signal killing threadUncaught signal kills entire process instead of specific thread
Use of undefined thread IDThread ID from failed thread creation used in subsequent thread functions
Automatic or thread local variable escaping from a threadVariable is passed from one thread to another without ensuring that variable stays alive through duration of latter thread
Thread-specific memory leakDynamically allocated thread-specific memory not freed before end of thread
Atomic load and store sequence not atomicVariable accessible between load and store operations
Atomic variable accessed twice in an expressionVariable can be modified between accesses
Function that can spuriously fail not wrapped in loopLoop checks failure condition after possible spurious failure
Function that can spuriously wake up not wrapped in loopLoop checks wake-up condition after possible spurious wake-up

Argomenti