Re: [lldb-dev] Weird results running lldb under Valgrind

2020-09-30 Thread 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 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

Re: [lldb-dev] Weird results running lldb under Valgrind

2020-09-30 Thread Dmitry Antipov via lldb-dev
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

Re: [lldb-dev] Weird results running lldb under Valgrind

2020-09-29 Thread Greg Clayton via lldb-dev
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. Doing a quick web search, this seems to be due to a mismatched libc++ and libstdc++: https://github.com/googl

Re: [lldb-dev] Weird results running lldb under Valgrind

2020-09-29 Thread Dmitry Antipov via lldb-dev
On 9/25/20 5:53 PM, Dmitry Antipov wrote: On 9/24/20 9:14 PM, Greg Clayton wrote: This must be a valgrind issue, there would be major problems if the OS isn't able to lock mutex objects correctly ("mutex is locked simultaneously by two threads"). It is getting confused by a recursive mutex? LL

Re: [lldb-dev] Weird results running lldb under Valgrind

2020-09-25 Thread Dmitry Antipov via lldb-dev
On 9/24/20 9:14 PM, Greg Clayton wrote: This must be a valgrind issue, there would be major problems if the OS isn't able to lock mutex objects correctly ("mutex is locked simultaneously by two threads"). It is getting confused by a recursive mutex? LLDB uses recursive mutexes.W LLDB's Predi

Re: [lldb-dev] Weird results running lldb under Valgrind

2020-09-24 Thread Greg Clayton via lldb-dev
This must be a valgrind issue, there would be major problems if the OS isn't able to lock mutex objects correctly ("mutex is locked simultaneously by two threads"). It is getting confused by a recursive mutex? LLDB uses recursive mutexes. > On Sep 24, 2020, at 1:55 AM, Dmitry Antipov via lldb-

[lldb-dev] Weird results running lldb under Valgrind

2020-09-24 Thread Dmitry Antipov via lldb-dev
Does anyone has an explanation of this weird run of 'valgrind --tool=drd': ==2715== drd, a thread error detector ==2715== Copyright (C) 2006-2017, and GNU GPL'd, by Bart Van Assche. ==2715== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==2715== Command: /home/antipov/.local/