RFR - Changes to address CCC 8014135: Support for statically linked agents
jeremymanson at google.com
Wed Jul 3 22:32:10 UTC 2013
I know that this is mentioned in the JEP, but does it really make sense to
have -agentpath work here, rather than just -agentlib? I would think that
specifying a full pathname and getting the library loaded out of the
launcher would be a little surprising to people who are basically saying
"please load this agent from the given path".
Also, in practice, we do something very similar at Google, and, when
testing, I find it occasionally useful to be able to say "please load this
agent on the command line via the agentpath I gave you, rather than loading
the one with the same name I baked into the launcher".
(FWIW, when we did this internally at Google, we added a special -XX flag
for when the agent is in the launcher. I know that you don't want to go
that way, though.)
On Wed, Jul 3, 2013 at 2:17 PM, BILL PITTORE <bill.pittore at oracle.com>wrote:
> These changes address bug 8014135 which adds support for statically linked
> agents in the VM. This is a followup to the recent JNI spec changes that
> addressed statically linked JNI libraries( 8005716).
> The JEP for this change is the same JEP as the JNI changes:
> http://openjdk.java.net/jeps/**178 <http://openjdk.java.net/jeps/178>
> Webrevs are here:
> The changes to jvmti.xml can also be seen in the output file that I placed
More information about the core-libs-dev