ROOT's Clang interpreter is not exception safe
Mu2e reports a situation where an error occurring while loading a GDML file results in ROOT attempting to double-unlock a mutex. Although this is an error in how exceptions are handled in ROOT's Clang, Philippe Canal reports that it can safely be ignored:
So if you could filter out (i.e. just print an error message or warning) anything from the regex "'T.*Lock::WriteUnLock" (or TReentrantRWLock::WriteUnLock), it solve the problem.
#1 Updated by Christopher Green 9 months ago
- % Done changed from 0 to 100
- Assignee set to Christopher Green
- Status changed from Accepted to Resolved
We believe this problem has been addressed upstream with https://github.com/root-project/root/commit/da77e82dc2bd4a0e3183ad424d6de7041d68d5d9. This fix will be included in the upcoming UPS package of ROOT v6_18_04d.