Searched refs:PTRACE_ATTACH (Results 1 – 7 of 7) sorted by relevance
38 other process (and its descendants) are allowed to call PTRACE_ATTACH49 0 - classic ptrace permissions: a process can PTRACE_ATTACH to any other56 with the inferior it wants to call PTRACE_ATTACH on. By default,60 an allowed debugger PID to call PTRACE_ATTACH on the inferior.64 with PTRACE_ATTACH, or through children calling PTRACE_TRACEME.66 3 - no attach: no processes may use ptrace with PTRACE_ATTACH nor via
242 object. For the PTRACE_ATTACH a read-write access is required.243 1 - exact: this is the policy that limits PTRACE_ATTACH. Attach is
21 #define PTRACE_ATTACH 16 macro
187 if (sys_ptrace(PTRACE_ATTACH, child, NULL, NULL) == -1) in main()
392 proc_ptrace_connector(task, PTRACE_ATTACH); in ptrace_attach()1092 if (request == PTRACE_ATTACH || request == PTRACE_SEIZE) { in SYSCALL_DEFINE4()1236 if (request == PTRACE_ATTACH || request == PTRACE_SEIZE) { in COMPAT_SYSCALL_DEFINE4()
205 if (ptrace_id == PTRACE_ATTACH) { in proc_ptrace_connector()
1038 ret = ptrace(PTRACE_ATTACH, tracee, NULL, 0); in tracer()