From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 12 15:40:54 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 685B7106566B; Sun, 12 Sep 2010 15:40:54 +0000 (UTC) Date: Sun, 12 Sep 2010 15:40:54 +0000 From: Alexander Best To: Mateusz Guzik Message-ID: <20100912154054.GA42409@freebsd.org> References: <4C8A81D9.5020905@rawbw.com> <20100910194600.GB60815@stack.nl> <20100912130801.GA23538@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Yuri , Jilles Tjoelker , freebsd-hackers@freebsd.org Subject: Re: Why I can't trace linux process's childs with truss? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2010 15:40:54 -0000 On Sun Sep 12 10, Mateusz Guzik wrote: > On Sun, Sep 12, 2010 at 3:08 PM, Alexander Best 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. looking good. could be post that patch as followup to yuri's PR? hope it gets committed soon. :) cheers. alex > > Regards, > -- > Mateusz Guzik -- a13x