On 8/21/19 5:47 PM, Mike Tancsa wrote:
> On 8/21/2019 6:38 PM, John Baldwin wrote:
>> On 8/21/19 9:08 AM, mike tancsa wrote:
>>> On 8/21/2019 12:00 PM, John Baldwin wrote:
>>>> dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] =
>>>> count()'
>>> Thanks, I am not familiar with dtrace at all. This command gives a
>>> syntax error
>>>
>>> 0(cage)# dtrace -n 'fbt::_gone_in:entry {
>>> @counts[curthread->td_proc->p_comm] = count()'
>>> dtrace: invalid probe specifier fbt::_gone_in:entry {
>>> @counts[curthread->td_proc->p_comm] = count(): syntax error near end of
>>> input
>>> 1(cage)#
>> Oops, I forgot the closing }. First, do "dtrace -l | grep _gone_in" to make
>> sure dtrace is loaded. You should see something like this:
>>
>> # dtrace -l | grep _gone_in
>> 87003 fbt kernel _gone_in entry
>> 87004 fbt kernel _gone_in return
>> 98682 fbt kernel _gone_in_dev entry
>> 98683 fbt kernel _gone_in_dev return
>>
>> Then this should work:
>>
>> # dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] =
>> count() }'
>> dtrace: description 'fbt::_gone_in:entry ' matched 1 probe
>>
> Thanks!
>
> # dtrace -l | grep _gone_in
> 15632 fbt kernel _gone_in entry
> 22693 fbt kernel _gone_in_dev entry
>
> # dtrace -n 'fbt::_gone_in:entry { @counts[curthread->td_proc->p_comm] =
> count() }'
> dtrace: description 'fbt::_gone_in:entry ' matched 1 probe
>
> However, It doesnt show anything after that even as I get the
> deprecation messages in dmesg
Can you hit Ctrl-C after seeing some of the messages? This trace won't
show any results until you exit dtrace.
--
John Baldwin
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
