emaste 41b576ab7d 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
..
2016-11-14 00:33:03 +00:00
2017-05-10 22:45:05 +00:00
2017-05-22 01:10:12 +00:00
2016-07-01 05:48:45 +00:00
2016-11-07 15:54:47 +00:00
2016-04-20 17:58:13 +00:00
2017-03-02 01:14:48 +00:00
2017-05-05 14:33:39 +00:00
2016-07-30 01:16:06 +00:00
2017-02-19 17:37:16 +00:00
2017-05-25 16:41:07 +00:00
2017-02-19 17:46:37 +00:00
2017-02-06 08:49:57 +00:00
2017-03-23 22:06:06 +00:00
2017-03-16 21:32:05 +00:00
2017-05-23 09:29:05 +00:00
2017-05-05 13:31:25 +00:00
2017-01-30 16:32:53 +00:00
2017-02-28 23:42:47 +00:00
2016-08-24 12:32:24 +00:00
2017-03-25 14:14:11 +00:00
2017-05-20 18:02:31 +00:00
2017-02-28 23:42:47 +00:00
2017-03-27 21:00:49 +00:00
2016-09-29 18:24:29 +00:00
2017-01-06 07:54:53 +00:00
2017-01-17 05:55:47 +00:00
2017-05-06 10:26:40 +00:00