On Jul 24, 2014, at 5:10 AM, skele...@lissyara.su via dtrace-discuss
<dtrace-discuss@lists.dtrace.org> wrote:
>
> Of course, I try it when application is running. Here is ouput:
>
> # ps -efc | grep java
> root 2398 1186 TS 49 12:05:28 pts/2 0:00 grep java
> root 1050 1 TS 59 Jul 21 ? 8:19 /bin/java -Xms256m
> -Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC -X
>
> # pargs 1050 | grep -i dtrace
> argv[7]: -XX:+ExtendedDTraceProbes
> argv[8]: -XX:+DTraceMethodProbes
> argv[9]: -XX:+DTraceAllocProbes
> argv[10]: -XX:+DTraceMonitorProbes
>
> # dtrace -n 'hotspot*::: { @[probename] = count(); }'
> dtrace: invalid probe specifier hotspot*::: { @[probename] = count(); }:
> probe description hotspot*::: does not match any probes
>
> So, lazy loading doesn't blame here.
I’m sorry, I should have looked more closely at my notes which actually use the
full name and not a glob. That makes a difference with lazy loading. Just to
be completely sure I ran a quick test:
root@oldboy:~# dtrace -n 'hotspot*::: { @[probename] = count(); }'
dtrace: invalid probe specifier hotspot*::: { @[probename] = count(); }: probe
description hotspot*::: does not match any probes
root@oldboy:~# pgrep java
12115
root@oldboy:~# dtrace -n 'hotspot12115::: { @[probename] = count(); }'
dtrace: description 'hotspot12115::: ' matched 66 probes
^C
root@oldboy:~# dtrace -l hotspot*::: | wc -l
76119
-Z
-------------------------------------------
dtrace-discuss
Archives: https://www.listbox.com/member/archive/184261/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184261/25769126-e243886f
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769126&id_secret=25769126-8d47a7b2
Powered by Listbox: http://www.listbox.com
