MFC r283889,r283891:
Clear p_stops when doing PT_DETACH and PROCFS_CTL_DETACH. Without this, if a process was being traced by truss(1), which uses different p_stops bits than gdb(1), the latter would misbehave because of the unexpected bits. Reported by: jceel Submitted by: sef Sponsored by: iXsystems, Inc.
This commit is contained in:
parent
5e00ed15eb
commit
201165c60b
@ -235,6 +235,7 @@ out:
|
||||
} else
|
||||
PROC_LOCK(p);
|
||||
p->p_oppid = 0;
|
||||
p->p_stops = 0;
|
||||
p->p_flag &= ~P_WAITED; /* XXX ? */
|
||||
sx_xunlock(&proctree_lock);
|
||||
|
||||
|
@ -963,6 +963,7 @@ kern_ptrace(struct thread *td, int req, pid_t pid, void *addr, int data)
|
||||
CTR1(KTR_PTRACE, "PT_DETACH: pid %d", p->p_pid);
|
||||
p->p_oppid = 0;
|
||||
p->p_flag &= ~(P_TRACED | P_WAITED | P_FOLLOWFORK);
|
||||
p->p_stops = 0;
|
||||
|
||||
/* should we send SIGCHLD? */
|
||||
/* childproc_continued(p); */
|
||||
|
Loading…
x
Reference in New Issue
Block a user