Date: Sun, 12 Sep 2010 17:01:09 +0200 From: Mateusz Guzik <mjguzik@gmail.com> To: Alexander Best <arundel@freebsd.org> Cc: Yuri <yuri@rawbw.com>, Jilles Tjoelker <jilles@stack.nl>, freebsd-hackers@freebsd.org Subject: Re: Why I can't trace linux process's childs with truss? Message-ID: <AANLkTikiWs9O%2B8%2BmwOaE4nVovT0yDQ3GvPO7E9H_MWkW@mail.gmail.com> In-Reply-To: <20100912130801.GA23538@freebsd.org> References: <4C8A81D9.5020905@rawbw.com> <20100910194600.GB60815@stack.nl> <20100912130801.GA23538@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 12, 2010 at 3:08 PM, Alexander Best <arundel@freebsd.org> wrote: > there's a PR related to this "issue" [1]. so is truss missing this > functionality or is this in fact a feature, because truss musn't be used on > any non freebsd executable? > Actually truss handles linux processes just fine, except for their children. :) Linux process can create a child using linux_clone syscall, but truss does not handle that case and this can be the problem that Yuri reported (since no log was provided, I can only guess). This trivial patch should fix this: http://student.agh.edu.pl/~mjguzik/truss-linux-forks.patch Tested on this simple program: http://student.agh.edu.pl/~mjguzik/fork.c If it still does not work, log generated by truss would be helfpul. Regards, -- Mateusz Guzik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikiWs9O%2B8%2BmwOaE4nVovT0yDQ3GvPO7E9H_MWkW>