Date: Mon, 25 Aug 2014 09:21:48 -0400 From: Eric van Gyzen <eric@vangyzen.net> To: freebsd-current@freebsd.org Subject: Re: ktrace -c behavior Message-ID: <53FB386C.9030800@vangyzen.net> In-Reply-To: <20140824235336.GR71691@funkthat.com> References: <53F79710.6090700@vangyzen.net> <20140822192034.GA71691@funkthat.com> <53F79971.4050802@vangyzen.net> <20140824235336.GR71691@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/24/2014 19:53, John-Mark Gurney wrote: > Eric van Gyzen wrote this message on Fri, Aug 22, 2014 at 15:26 -0400: >> On 08/22/2014 15:20, John-Mark Gurney wrote: >>> Eric van Gyzen wrote this message on Fri, Aug 22, 2014 at 15:16 -0400: >>>> 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. >>> and/or just add specified: >>> Clear the specified trace points ... >> But what if I didn't specify them? > You specified the default by not specificly specifing any different > ones.. :) Confused? :) Amused. :) > or maybe selected? Perhaps, but I didn't select them, either. My original suggestion is more--dare I use this word again--specific. It explains exactly how the command behaves. Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53FB386C.9030800>