Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
When instrumenting code with kelinci, I often get:
For now I just make sure it will use the non-instrumented classes when it fails in my fork (see floyd-fuh@32f405e), however, I think that's not the best option. Any idea why it could fail? Are there any dependencies that could be missing during instrumentation or anything like that?
Hi Floyd, thanks for your feedback! Is the "com.otherexample" package in example.jar? Kelinci uses ASM for instrumentation. ASM requires superclasses of the classes to instrument to be on the classpath. Adding the "com.otherexample" package to the classpath should fix this.
The "com.otherexample" package is not in example.jar and you are probably right. However, in my case I was simply too lazy and just skipped instrumentation, in most cases instrumenting 99% of the code is probably fine.
Ok, I sent you a pull request #5 that catches the errors