> > at least from the source i have, writing to p->hang after
> > the fork isn't going to do anything. p->hang is only consulted
> > in sysexec. i think you need to add the same test in sysfork.
>
> It is only supposed to be consulted in sysexec. Hang just means that
> the next exec will result
On Sun, Feb 13, 2011 at 7:50 PM, erik quanstrom wrote:
> at least from the source i have, writing to p->hang after
> the fork isn't going to do anything. p->hang is only consulted
> in sysexec. i think you need to add the same test in sysfork.
It is only supposed to be consulted in sysexec. Ha
On Sun Feb 13 19:34:25 EST 2011, rminn...@gmail.com wrote:
> there's a race in ratrace: programs can escape. The reason is that the
> parent forks a child and writes stop to its ctl file. But the child
> can run any number of system calls -- even to completion -- before the
> parent writes that sto
there's a race in ratrace: programs can escape. The reason is that the
parent forks a child and writes stop to its ctl file. But the child
can run any number of system calls -- even to completion -- before the
parent writes that stop command. I'm seeing this on arm.
The fix is simple, in the child
