This was my fault. See
http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/b1a2afa37ec4
I simply forgot to update the jdk (though I did remember to update jmm.h,
of course, because I added . The changes isn't functional, just a
formal parameter name change to match the jni call.
If we can
Actually this is news to me. I thought that they were identical when
I checked it into the jdk repo. Might be that the someone (likely me)
changed the jvmti.xml file in the hotspot repo sometime afterward and
forgot to re-sync with the jdk. Can we just re-copy it over with the
next put
On 4/5/2011 10:03 AM, Kelly O'Hair wrote:
Could someone from the serviceability team copy in the latest generated jvmti.h
file from a hotspot build
into the jdk repository? Or was that done already?
-kto
Looks like Keith updated it back in Jan...
$ hg log src/share/javavm/export/jvmti.h
Could someone from the serviceability team copy in the latest generated jvmti.h
file from a hotspot build
into the jdk repository? Or was that done already?
-kto
