From owner-freebsd-current@FreeBSD.ORG  Fri Aug 22 19:16:34 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D919243C
 for <freebsd-current@freebsd.org>; Fri, 22 Aug 2014 19:16:34 +0000 (UTC)
Received: from smtp.vangyzen.net (hotblack.vangyzen.net
 [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f])
 by mx1.freebsd.org (Postfix) with ESMTP id BD7813919
 for <freebsd-current@freebsd.org>; Fri, 22 Aug 2014 19:16:34 +0000 (UTC)
Received: from marvin.lab.vangyzen.net (c-24-125-214-90.hsd1.va.comcast.net
 [24.125.214.90])
 by smtp.vangyzen.net (Postfix) with ESMTPSA id A21EB56436
 for <freebsd-current@freebsd.org>; Fri, 22 Aug 2014 14:16:33 -0500 (CDT)
Message-ID: <53F79710.6090700@vangyzen.net>
Date: Fri, 22 Aug 2014 15:16:32 -0400
From: Eric van Gyzen <eric@vangyzen.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: ktrace -c behavior
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2014 19:16:34 -0000

What behavior would you expect from this sequence of commands?

    ktrace -tw -p 1234
    ktrace -c -p 1234

Based on this...

     -c      Clear the trace points associated with the specified file
or processes.

...I would expect the second command to clear the trace point for
context switches.  It doesn't.  I have to specify -tw with the -c to get
that behavior.  This makes sense; it's just not what I was expecting.

Assuming we want to keep this behavior, can we clarify the -c flag in
man page?  I would suggest:

    If the -t flag is not specified, clear the default set of trace points.

Thanks,

Eric