On Oct 24, 2012, at 1:08 PM, Jochen Theodorou wrote:
> what do you suggest as workaround?
You could force the class to be initialized when the MH is created. This can
be done with Class.forName. It would not exactly give you the semantics you
want, since the init would happen early.
Or, you could wrap the buggy MH in a MH which first forces initialization.
With a switchpoint you can make it a once-only event (per thread, at least).
— John
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
