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
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
When you say "execute binary code", where exactly is this code being
executed? Is it executed by launching another process?
Lldb will not automatically debug all child process spawned by your
process -- they will run freely.
The SIGCHLDs are not coming from lldb -- they are signals which all
proc
