ktrace -c behavior

[Eric van Gyzen]

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