Re: kern/52117: ptrace(2) PTRACE_FORK fails on some platforms

["Kamil Rytarowski" <n54%gmx.com@localhost>]

The following reply was made to PR kern/52117; it has been noted by GNATS.

From: "Kamil Rytarowski" <n54%gmx.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/52117: ptrace(2) PTRACE_FORK fails on some platforms
Date: Tue, 28 Mar 2017 16:44:50 +0200

 This child_return has been added a while ago.
 
 I'm not sure if we are supposed to interact with this in the context of emulated ABIs.
 
 Author: christos <christos>
 Date:   Fri Sep 2 20:01:20 2011 +0000
 
     If the process is traced, resulting from a PTRACE_FORK inherited setting,
     stop it right now.
     
     XXX[1]: Cannot make this MI, because I cannot wrap child_return because there
     is MD code that checks fun == child_return. I think it is better to have an
     mi child_return() and add a cpu_child_return()?
     XXX[2]: Why do we need to stop so early? Perhaps stopping just after exec
     is better?
 
 
 https://github.com/jsonn/src/commit/ccb6242edfcac843fd3d6bdf5b514ac79bad889d
 
 Answering why do we need to stop early, in debuggers we want to stop as early as
 possible, before constructors will fire and with ability to set there a trap.