I've been running the cvs JIT_SUPPORT branch from a couple of days back
on and off for a day or so now. Firstly, is there any docs regarding
the new JIT language profiling? (I'm not sure if/when I'm meant to run
opjitconv for example - no man page there yet). The documentation for
other areas of oprofile (covering the implementation details of the
kernel interface for example) are excellent - would be great to have
such an in-depth reference for the new code too.
Is the new code known to work on Sun's Java implementation? I see IBM
email addresses on checkin notes, so guess you guys are using JRocket
for testing? In my profiling results I see several JVMTI calls, so I
assume its going down some of the new code paths, but actual profile
result output from "opreport -l" doesn't show me Java app functions as
I'd kinda hoped.
I've also been hitting what look like unexpected early exits from the
oprofile daemon - not sure if this is the new code or not - is there
any good way to debug this? (would a daemon core file be put in some
standard place? easy way to get oprofiled to run under gdb when its
started from opcontrol? how do you folks usually tackle this class
of problem? - thanks!)
[nathans@... ~]$ sudo opcontrol --start
[nathans@... ~]$ sleep 30
[nathans@... ~]$ sudo opcontrol --stop
dump fail: daemon died during last run ?
Detected stale lock file. Removing.
This doesn't happen every time - maybe 1 out of 10 runs or so, not
sure if there's any pattern. Running in default h/ware event counter
mode on various x86 class processors (all in 32 bit mode).