Messages in this thread | | | Date | Thu, 30 Apr 1998 15:39:47 +0200 | From | Alexander Kjeldaas <> | Subject | ptrace and SIGCONT |
| |
When a process is ptraced, it will often be set to TASK_STOPPED by the kernel. However, any process in the same session can start the ptraced process by sending a SIGCONT signal. Is this intended behaviour? IMO, it seems like we loose some control over the ptraced process by allowing this.
The reason I bring this up is because I want to use ptrace to set capabilities on a process to avoid races. This requires that the ptracing process actually has control over the ptraced process.
astor
-- Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway http://www.guardian.no/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |