Skip to content

Commit 4a24cf0

Browse files
committed
docs
1 parent c625af8 commit 4a24cf0

File tree

3 files changed

+0
-3
lines changed

3 files changed

+0
-3
lines changed

c/cert/src/rules/CON30-C/CleanUpThreadSpecificStorage.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ This query implements the CERT-C rule CON30-C:
55
> Clean up thread-specific storage
66
77

8-
98
## Description
109

1110
The `tss_create()` function creates a thread-specific storage pointer identified by a key. Threads can allocate thread-specific storage and associate the storage with a key that uniquely identifies the storage by calling the `tss_set()` function. If not properly freed, this memory may be leaked. Ensure that thread-specific storage is freed.

c/cert/src/rules/CON34-C/AppropriateThreadObjectStorageDurations.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ This query implements the CERT-C rule CON34-C:
55
> Declare objects shared between threads with appropriate storage durations
66
77

8-
98
## Description
109

1110
Accessing the automatic or thread-local variables of one thread from another thread is [implementation-defined behavior](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-implementation-definedbehavior) and can cause invalid memory accesses because the execution of threads can be interwoven within the constraints of the synchronization model. As a result, the referenced stack frame or thread-local variable may no longer be valid when another thread tries to access it. Shared static variables can be protected by thread synchronization mechanisms.

c/cert/src/rules/CON34-C/ThreadObjectStorageDurationsNotInitialized.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ This query implements the CERT-C rule CON34-C:
55
> Declare objects shared between threads with appropriate storage durations
66
77

8-
98
## Description
109

1110
Accessing the automatic or thread-local variables of one thread from another thread is [implementation-defined behavior](https://wiki.sei.cmu.edu/confluence/display/c/BB.+Definitions#BB.Definitions-implementation-definedbehavior) and can cause invalid memory accesses because the execution of threads can be interwoven within the constraints of the synchronization model. As a result, the referenced stack frame or thread-local variable may no longer be valid when another thread tries to access it. Shared static variables can be protected by thread synchronization mechanisms.

0 commit comments

Comments
 (0)