Re: [lldb-dev] Weird results running lldb under Valgrind
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 Predicate.h uses plain std::mutex, which is not recursive, and
std::lock_guard/std::unique_lock
on top of it.
This needs more digging in because the latest Valgrind snapshot reports the same
"impossible" condition.
Dmitry
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 47647] New: Use fzf (fuzzy finder) for search backward through history
https://bugs.llvm.org/show_bug.cgi?id=47647 Bug ID: 47647 Summary: Use fzf (fuzzy finder) for search backward through history Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: bruno.card...@gmail.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org Pretty much what the summary says. This would be really handy for quick searching history. Not sure how easy is to hook this up to LLDB but several tools (bash, zsh, vim, ...) can currently leverage this. Fuzzy Finder: https://github.com/junegunn/fzf -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 47647] Use fzf (fuzzy finder) for search backward through history
https://bugs.llvm.org/show_bug.cgi?id=47647 Jonas Devlieghere changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |jdevliegh...@apple.com -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 47648] New: Lack of persistent history
https://bugs.llvm.org/show_bug.cgi?id=47648 Bug ID: 47648 Summary: Lack of persistent history Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: bruno.card...@gmail.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org I've noticed that whenever LLDB crashes I lose all the history from a session. This is fine for quick sessions but I often leave sessions open for days or weeks and it's pretty sad to lose all the joy. I looked up but didn't find a way to have LLDB regularly flushing that to disk (or even a command to allow me to do that myself). Any solutions along those lines would be great to have. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
