You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a program which has several threads that log. When running under thread sanitizer, we see races related to google::LogMessageTime::CalcGmtOffset(), frequently with this malloc/free pattern. It seems like glog is intended to behave well under thread sanitizer and my understanding is that locking outside glog is not necessary. I would appreciate any advice to understand why this is happening. We can suppress this location, but it would be nice to have a better understanding of what is going on here.
I'm working on a program which has several threads that log. When running under thread sanitizer, we see races related to
google::LogMessageTime::CalcGmtOffset()
, frequently with this malloc/free pattern. It seems like glog is intended to behave well under thread sanitizer and my understanding is that locking outside glog is not necessary. I would appreciate any advice to understand why this is happening. We can suppress this location, but it would be nice to have a better understanding of what is going on here.The text was updated successfully, but these errors were encountered: