Date: Fri, 13 Sep 2019 15:03:56 -0400 From: Ryan Stone <rysto32@gmail.com> To: Mark Johnston <markj@freebsd.org> Cc: Mariusz Zaborski <oshogbo@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Deadlock involving truss -f, pdfork() and wait4() Message-ID: <CAFMmRNzZT4LFLEUY6viNttLaJs14xm1JZBzKTmpKgAhjNZOUtw@mail.gmail.com> In-Reply-To: <20190913183718.GC84156@raichu> References: <CAFMmRNwRWZsQhMSY7MwS2kU-qNJ0%2BPk676mi59_Y3QsbcEmPVQ@mail.gmail.com> <CAGOYWV-v1-F3dWQovdj5TZMZeBFifDm020AXnPYdZSHPKLG4SA@mail.gmail.com> <CAFMmRNzhsk-1BO6iyJz7_qtgnRqC%2BfPpYSuQnxEZyno%2BO1K71Q@mail.gmail.com> <20190913183718.GC84156@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
As Conrad has pointed out, it's an explicit PID. The test completes successfully when not run under truss -f. On Fri, Sep 13, 2019 at 2:37 PM Mark Johnston <markj@freebsd.org> wrote: > > On Fri, Sep 13, 2019 at 02:12:56PM -0400, Ryan Stone wrote: > > This gets me a little further but now the wait4 call by the parent > > never reaps the child and instead blocks forever: > > Does it perform a wildcarded wait(), or does it explicitly specify the > PID of the child? By design, the former will not return children > created by pdfork().
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNzZT4LFLEUY6viNttLaJs14xm1JZBzKTmpKgAhjNZOUtw>