Ed Maste b08e22797d lldb: map TRAP_CAP to a trace trap ... In the absense of a more specific handler for TRAP_CAP (generated by ENOTCAPABLE or ECAPMODE while in capability mode) treat it as a trace trap. Example usage (testing the bug in PR219173): % proccontrol -m trapcap lldb usr.bin/hexdump/obj/hexdump -- -Cv -s 1 /bin/ls ... (lldb) run Process 12980 launching Process 12980 launched: '.../usr.bin/hexdump/obj/hexdump' (x86_64) Process 12980 stopped * thread #1, stop reason = trace frame #0: 0x0000004b80c65f1a libc.so.7`__sys_lseek + 10 ... In the future we should have LLDB control the trapcap procctl itself (as it does with ASLR), as well as report a specific stop reason. This change eliminates an assertion failure from LLDB for now.		2017-05-25 16:41:07 +00:00
..
docs	Merge LLDB 3.8	2016-01-04 01:16:32 +00:00
include/lldb	Merge llvm, clang, lld and lldb release_40 branch r292009. Also update	2017-01-14 22:12:13 +00:00
source	lldb: map TRAP_CAP to a trace trap	2017-05-25 16:41:07 +00:00
tools	Merge llvm, clang, lld and lldb trunk r291274, and resolve conflicts.	2017-01-06 20:24:06 +00:00
FREEBSD-Xlist	Update lldb to upstream trunk r242221.	2015-09-06 15:21:47 +00:00
LICENSE.TXT