summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'README.md')
-rw-r--r--README.md12
1 files changed, 10 insertions, 2 deletions
diff --git a/README.md b/README.md
index 8e2766b..ecbe634 100644
--- a/README.md
+++ b/README.md
@@ -322,7 +322,11 @@ protection makes the kernel refuse syscalls that write there, and soft-dirty
bits still need the compare, a page at a time. **Syscalls** go through
SIGSYS because the kernel then needs no second process: the cost is two
signal frames, on a stack of the agent's so that it works on threads with
-almost none.
+almost none. A handler starts with the kernel's defaults, not the thread's
+rights to memory behind protection keys (PKRU) nor its floating-point
+modes; the agent's handlers take the thread's back first, so that a syscall
+made for it, a thread cloned for it and a watched page read for it are as
+the thread would have them (V8 keeps its code space behind a key).
Measured (`zig build bench-agent -Doptimize=ReleaseFast`, an i7-11700, each
loop 10^5 to 5 10^6 times; bytes are the recording's):
@@ -350,7 +354,11 @@ Limits: a hooked function called with SIGTRAP blocked dies (not under
do not unwind through a hooked call; a pointer the kernel would answer with
EFAULT faults in the handler; syscalls made from the vDSO never enter the
kernel and are not seen, as under ptrace; a target that needs SIGSYS or its
-own alternate signal stack is told it has them.
+own alternate signal stack is told it has them. `--alloc` sees calls that
+reach libc's allocator by name: a program that brings its own `malloc` and
+binds it inside itself (d8 does) shows none, and `--hook malloc` is the way
+to see those. A target that dies under the agent dumps core like any other,
+which for a V8 takes half a minute; `ulimit -c 0` if that is not wanted.
## The kernel's view