[lldb-dev] Weird results running lldb under Valgrind

Dmitry Antipov via lldb-dev lldb-dev at lists.llvm.org
Wed Sep 30 02:53:36 PDT 2020

On 9/29/20 11:40 PM, Greg Clayton wrote:

> How could LLDB even function then? We are using the standard std::mutex + std::condition workflow here. Not sure how LLDB could even function if it locking was nor working as expected.

Well, obviously this is an issue (and probably the same one) with debugging tools.

> Doing a quick web search, this seems to be due to a mismatched libc++ and libstdc++:
> https://github.com/google/sanitizers/issues/1259

Nice. So if your libstdc++ is new enough to use pthread_cond_clockwait(), both TSan and
valgrind produces weird results just because they can handle pthread_cond_timedwait() only.


More information about the lldb-dev mailing list