jhmanson

Not right now. If you are building from source, it's pretty easy to hardcode, see: https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationInstrumenter.java#L48 Otherwise, pull requests (with tests) probably acceptable. IIRC we haven't tried to accept anything...

It's probably okay to have it in there, as long as both methods were supported. Note that that approach is very implementation-dependent, so we'd have to tell people "try it...

Note that both this tool and JEP-331 came from the same team, and that this tool predates JEP-331 by about a decade. We developed that JEP because we couldn't do...

Allocation instrumentation runs the handler when the new bytecode (or equivalent) is called. So, it is handled in that case. Constructor instrumentation doesn't handle that case. I probably won't have...

I guess I'm not sure I understand the problem. "try" and "catch" and "finally" are source level constructs, not bytecode level ones. In bytecode, you have an exception table that...