RFR: MethodHandles.Lookup. Wrong access verification

[Sebastian Sickelmann]

Hi,

some days ago i had written[0] that i maybe found a bug in access
verification in MethodHandles.Lookup.

Now i produces webrev's for the two repos jdk and hotspot.

In the jdk webrev [1] I implemented some additional tests.

In the hotspot webrev [2] I tried to fix the wrong behavior. I am not
sure if it is the right place to fix this.
It is more an proof-of-concept--like--reverse-engineering*//*
<https://www.google.de/search?espv=210&es_sm=122&q=reverse+engineering&spell=1&sa=X&ei=8PWcUq2cE6rCyQPLqID4BQ&ved=0CCwQvwUoAA>-fix
that fixes the symptom, and i do not fully
understand all the things in the patched source. In fact i think that we
can move line 187 to 182 instead
of chaning line 245 in methodHandles.cpp. But as i said i do not fully
understand init_method_MemberName
and all those CallInfo::vtable_call / CallInfo::itable_call /
CallInfo::direct_call differences.

Hope my works helps solving this issue. And i hope it is an issue. And i
hope my fix isn't breaking anything else
so that it was enough to test my fix against my new testcase in
MethodHandlesTest.testFindPrivate

Kind regards
Sebastian

[0]
http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2013-November/010228.html
[1]
https://dl.dropboxusercontent.com/u/43692695/oss-patches/openjdk8/MethodHandles.Lookup/webrev_jdk/index.html
[2]
https://dl.dropboxusercontent.com/u/43692695/oss-patches/openjdk8/MethodHandles.Lookup/webrev_hotspot/index.html