From owner-freebsd-current@FreeBSD.ORG Wed Jan 16 02:55:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9678379D; Wed, 16 Jan 2013 02:55:16 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5CFCD96; Wed, 16 Jan 2013 02:55:16 +0000 (UTC) Received: by mail-oa0-f50.google.com with SMTP id n16so938566oag.9 for ; Tue, 15 Jan 2013 18:55:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/+/mgRkKV/tyjsPZwIa/UZDtr5ordNP4/pbYyJWIP4I=; b=IML7tMizihFnxeRmduSfMZUxN8tBTTrfCXR3ue8Rol/qP6ggB95JmBMrB7KjNNRxJB /j8kyXqEgxmWKSOWpFdsxY/cTc3Hp5hGZZbiCckBc27vTWTMYUIl1ZjevzKcUBNrczei DIqlo+tEP9eXp6VS5am3XOJ9/Cd9JSN62fWRYRY2ugF7JI5TBjSDzBYRoQj8W163CsyC mxAPW8jtiXMgA/s7wDockyc8eUkS3AJwZbDCvacuQk0zQ/jpKJmd3ysNu+pwlmcHsVVD LPmvrWHCllbDIIRFQhNGi+eP7uChzMcvBR+cksm3FfG160j4E9l0kjC3cTvZmrnJ0TCJ YeJw== MIME-Version: 1.0 Received: by 10.60.0.165 with SMTP id 5mr58176161oef.128.1358304911619; Tue, 15 Jan 2013 18:55:11 -0800 (PST) Received: by 10.76.107.241 with HTTP; Tue, 15 Jan 2013 18:55:11 -0800 (PST) In-Reply-To: <20130115225305.GA12294@stack.nl> References: <4850A09B-A054-4B38-891C-06673F7195B2@gmail.com> <20130115225305.GA12294@stack.nl> Date: Tue, 15 Jan 2013 18:55:11 -0800 Message-ID: Subject: Re: ktrace -d broken on current/stable-9 From: Garrett Cooper To: Jilles Tjoelker Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current , kib@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2013 02:55:16 -0000 On Tue, Jan 15, 2013 at 2:53 PM, Jilles Tjoelker wrote: > On Mon, Jan 14, 2013 at 06:48:13PM -0800, Garrett Cooper wrote: >> I tried using ktrace on a kernel compiled a week ago, and it appears >> to not be following forks like it should on amd64: > >> # ktrace -d ./regress -l >> [snip] > >> Not sure how it broke, but it was working a couple months ago (in >> particular I remember it working either around October or November), >> and the bug seems to have worked its way back to 9-STABLE (I'm running >> into the same problem if I do ktrace -d, enter a shell, then exec >> another shell from that shell). Haven't spent the time to bisect the >> commits looking for the culprit (yet), but if need be I'll trace down >> the culprit sometime this week. > >> truss works, so it doesn't seem like ptrace(2) is broken. > > ktrace -d is not really useful in the synopsis with a command. It only > means that the child processes of ktrace (at a time just before it > executes the utility) should be traced as well. This is almost always an > empty set, unless you do things like > cmd1 & ktrace -d cmd2 > which will trace cmd2 and part of cmd1. > > You probably want ktrace -i. Dangit -- forgot about that option. Ok, PEBKAC award for me. Thanks, -Garrett