From what I understand, it's possible for multiple threads to request
a specific language runtime (e.g. CPPLanguageRuntime). This leads to a data
race.
Details
Details
- Reviewers
jingham JDevlieghere compnerd clayborg - Commits
- rZORG005684738fe3: [Target] Protect Processes' language runtimes map with a mutex
rG005684738fe3: [Target] Protect Processes' language runtimes map with a mutex
rG74eb76f6c31e: [Target] Protect Processes' language runtimes map with a mutex
rLLDB361442: [Target] Protect Processes' language runtimes map with a mutex
rL361442: [Target] Protect Processes' language runtimes map with a mutex
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
I would use a lock_guard + lexical scope instead of locking/unlocking. Is there a reason not to here?