https://bugs.llvm.org/show_bug.cgi?id=35488
Bug ID: 35488
Summary: [Meta] tracking test suite failure on Mac OS
Product: lldb
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
https://bugs.llvm.org/show_bug.cgi?id=35484
Davide Italiano changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://bugs.llvm.org/show_bug.cgi?id=35484
Greg Clayton changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.llvm.org/show_bug.cgi?id=35484
Bug ID: 35484
Summary: Debug server can't be built on High Sierra
Product: lldb
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Yes, I can run LLDB under at least ASan and TSan.
Pity, the backend part (lldb-server) broke after refactoring the code in
recent months. I'm observing an early NULL pointer deference from NetBSD
Process Plugin - this is unrelated to the previous stability bugs that
inspired me to get the sanitize
Have you been able to run lldb under any sanitizers yet?
On Thu, Nov 30, 2017 at 12:24 PM Kamil Rytarowski via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hello,
>
> I've finished the LLVM TSan porting:
>
> https://blog.netbsd.org/tnf/entry/the_llvm_thread_sanitizer_has
>
> Next goal:
> Finish MS
Hello,
I've finished the LLVM TSan porting:
https://blog.netbsd.org/tnf/entry/the_llvm_thread_sanitizer_has
Next goal:
Finish MSan followed by the switch to LLDB/NetBSD corrections.
signature.asc
Description: OpenPGP digital signature
___
lldb-dev m
These sort of issues I have faced in the past and in my case the
reason was I used the incorrect host triple while building LLDB (LLVM
etc).
Example:
Assuming you are using GCC/G++ compiler to build LLVM+LLDB, I would
set the LLVM_HOST_TRIPLE to the one used in the library path and not
essentia
