Expand description
Flags used as an argument to many system calls
Structs§
Constants§
- Prevents the kernel from jumping the context to the signal trampoline, but otherwise has absolutely no effect on which signals are blocked etc. Meant to be used for short-lived critical sections inside libc.
- For userspace-backed mmaps, return from the mmap call before all pages have been provided by the scheme. This requires the scheme to be trusted, as the current context can block indefinitely, if the scheme does not respond to the page fault handler’s request, as it tries to map the page by requesting it from the scheme.
- Indicates whether the funmap call must implicitly do an msync, for the changes to become visible later.
- Sent when current-addrspace is changed, allowing the tracer to reopen the memory file.
- Sent when a child is cloned, giving you the opportunity to trace it. If you don’t catch this, the child is started as normal.
- Special meaning, depending on the event. Usually, when fired before an action, it will skip performing that action.
- Stop on a software breakpoint, such as the int3 instruction for x86_64.
- Stop just before exiting for good.
- Stop after a syscall is handled.
- Stop before a syscall is handled. Send PTRACE_FLAG_IGNORE to not handle the syscall.
- Stop before a signal is handled. Send PTRACE_FLAG_IGNORE to not handle signal.
- Stop after exactly one instruction. TODO: This may not handle fexec/signal boundaries. Should it?
Functions§
- True if status indicates a core dump was created.
- If wifexited(status), the exit status.
- True if status indicates the child continued after a stop.
- True if status indicates normal termination.
- True if STATUS indicates termination by a signal.
- True if status indicates the child is stopped.
- If wifstopped(status), the signal that stopped the child.
- If wifsignaled(status), the terminating signal.