StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Added note about detached threads racing with global destructors

Browse Source
This commit is contained in:
Anthony Williams 2016-10-04 16:43:47 +01:00 committed by Jonathan Wakely
parent ce93de647a
commit f15d001ba0
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CppCoreGuidelines.md
View File

@ -12287,6 +12287,12 @@ By "bad" we mean that a `thread` may use a pointer after the pointed-to object i
The fact that `thread`s run concurrently doesn't affect the lifetime or ownership issues here; The fact that `thread`s run concurrently doesn't affect the lifetime or ownership issues here;
these `thread`s can be seen as just a function object called from `some_fct`. these `thread`s can be seen as just a function object called from `some_fct`.
##### Note
Even objects with static storage duration can be problematic if used from detached threads: if the
thread continues until the end of the program, it might be running concurrently with the destruction
of objects with static storage duration, and thus accesses to such objects might race.
##### Enforcement ##### Enforcement
In general, it is undecidable whether a `detach()` is executed for a `thread`, but simple common cases are easily detected. In general, it is undecidable whether a `detach()` is executed for a `thread`, but simple common cases are easily detected.