[lldb-dev] Weird results running lldb under Valgrind

[Greg Clayton via lldb-dev]

Glad we know why at least! Thanks for bringing this to our attention.

Greg

> On Sep 30, 2020, at 2:53 AM, Dmitry Antipov <dmantipov at yandex.ru> wrote:
> 
> 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.
> 
> Dmitry
>