Re: [lldb-dev] Weird results running lldb under Valgrind
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 ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [11.0.0 Release] Release Candidate 5 is here
Hello again, We had to pick up another bug fix, so here is another release candidate: llvmorg-11.0.0-rc5 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5 Pre-built binaries will be added as they become ready. Please file reports for any bugs you find as blockers of https://llvm.org/pr46725 Release testers, if you still have cycles (perhaps you didn't even have time to start rc4 yet), please run the test script, share your results, and upload binaries. As mentioned above, this rc is very similar to the previous one. There are no open blockers, so it could be the last release candidate. Thanks, Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] Weird results running lldb under Valgrind
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 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 > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
