[lldb-dev] LLDB/NetBSD - Status June 2018

[Kamil Rytarowski via lldb-dev]

MKSANITIZER - bug detector software integration with the NetBSD userland

I've finished the integration of sanitizers with the distribution build
framework. A bootable and installable distribution is now available,
verified with Address Sanitizer, with Undefined Behavior Sanitizer, or
with both concurrently. A few dozen bugs were detected and the majority
of them addressed.


Plan for the next milestone

The ptrace(2) tasks have been preempted by the suspended work on
sanitizers, in order to actively collaborate with the Google Summer of
Code students (libFuzzer integration with userland, KUBSan, KASan).

I have planned the following tasks before returning back to the
ptrace(2) fixes:

 * upgrade base Clang/LLVM, libcxx, libcxxabi to at least 7svn (HEAD)
(needs cooperation with Joerg Sonnenberger)
 * compiler-rt import and integration with base (needs cooperation with
Joerg Sonnenberger)
 * merge TSan, MSan and libFuzzer ATF tests
 * prepare MKSANITIZER readme
 * kernel-asan port
 * kernel-ubsan port
 * switch syscall(2)/__syscall(2) to libc calls
 * upstream local patches, mostly to compiler-rt
 * develop fts(3) interceptors (MSan, for ls(1), find(1), mtree(8)
 * investigate and address the libcxx failing tests on NetBSD
 * no-ASLR boot.cfg option, required for MKSANITIZER

My plan for the next milestone is to reduce the the list and keep
actively collaborating with the summer students.


http://blog.netbsd.org/tnf/entry/mksanitizer_bug_detector_software_integration


This work was sponsored by The NetBSD Foundation.



signature.asc
Description: OpenPGP digital signature
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] July LLVM bay-area social is *not* this Thursday!

[George Burgess IV via lldb-dev]

Just a friendly reminder that, due to popular demand, we've moved this
month's bay-area social to 12-Jul. I'll send out the regular email
announcing it next week. :)

Have a great week (and happy 4th, for those who celebrate it!),
George
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] lldb-mi doesn't propagate host environment variables

[Jim Ingham via lldb-dev]

In lldb, this behavior is controlled by the setting:

target.inherit-env

Passing debugger environment is equal parts handy (getting a DISPLAY variable 
right for instance) and a cause for confusion.  Not sure which is the most 
useful default.  lldb defaults to true.  But I can see an argument that for a 
server type program like lldb-mi it is better to be explicit about it.

Jim


> On Jun 29, 2018, at 5:03 AM, k.baladurin via lldb-dev 
>  wrote:
> 
> Hello!
> 
> lldb-mi doesn't propagate host environment variables while lldb does it:
> 
> $ cat env.c
> #include 
> #include 
> 
> int main()
> {
> printf("VAR = %s\n", getenv("VAR"));
> return 0;
> }
> $ gcc env.c -o env
> $ /home/kbaladurin/Downloads/llvm-x64-7.0/bin/lldb -v
> lldb version 7.0.0
> $ VAR=1 /home/kbaladurin/Downloads/llvm-x64-7.0/bin/lldb env
> (lldb) target create "env"
> Current executable set to 'env' (x86_64).
> (lldb) r
> Process 13139 launched: '/home/kbaladurin/Desktop/tests/env' (x86_64)
> VAR = 1
> Process 13139 exited with status = 0 (0x)
> (lldb) ^D
> $ VAR=1 /home/kbaladurin/Downloads/llvm-x64-7.0/bin/lldb-mi
> (gdb)
> -file-exec-and-symbols env
> ^done
> (gdb)
> =library-loaded,id="/home/kbaladurin/Desktop/tests/env",target-name="/home/kbaladurin/Desktop/tests/env",host-name="/home/kbaladurin/Desktop/tests/env",symbols-loaded="0",loaded_addr="-",size="0"
> -exec-run
> ^running
> =thread-group-started,id="i1",pid="13176"
> (gdb)
> =thread-created,id="1",group-id="i1"
> =thread-selected,id="1"
> (gdb)
> =library-loaded,id="/lib/x86_64-linux-gnu/ld-2.23.so",target-name="/lib/x86_64-linux-gnu/ld-2.23.so",host-name="/lib/x86_64-linux-gnu/ld-2.23.so",symbols-loaded="1",symbols-path="/usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so",loaded_addr="-",size="0"
> (gdb)
> =library-loaded,id="[vdso]",target-name="[vdso]",host-name="[vdso]",symbols-loaded="1",symbols-path="",loaded_addr="0x77ffa000",size="0"
> (gdb)
> =library-loaded,id="/home/kbaladurin/Desktop/tests/env",target-name="/home/kbaladurin/Desktop/tests/env",host-name="/home/kbaladurin/Desktop/tests/env",symbols-loaded="0",loaded_addr="-",size="0"
> (gdb)
> *running,thread-id="all"
> (gdb)
> (gdb)
> =library-loaded,id="/lib/x86_64-linux-gnu/libc.so.6",target-name="/lib/x86_64-linux-gnu/libc.so.6",host-name="/lib/x86_64-linux-gnu/libc.so.6",symbols-loaded="1",symbols-path="/usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so",loaded_addr="-",size="0"
> (gdb)
> =library-loaded,id="/lib/x86_64-linux-gnu/libc.so.6",target-name="/lib/x86_64-linux-gnu/libc.so.6",host-name="/lib/x86_64-linux-gnu/libc.so.6",symbols-loaded="1",symbols-path="/usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so",loaded_addr="-",size="0"
> @"VAR = (null)\r\n"
> (gdb)
> =thread-exited,id="1",group-id="i1"
> =thread-group-exited,id="i1",exit-code="0"
> *stopped,reason="exited-normally"
> (gdb)
> 
> Is it expected behavior?
> 
> Thank you!
> 
> BR,
> Konstantin Baladurin
> 
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev