Explicit disl-bypass.jar load
When executing the analysis I sometimes forget to place the
disl-bypass.jar into the observed program classpath, or the jar file is not present at its expected location
due to the build errors for example. In such cases the observed machine dies with a core dump by the NoClassDefFound exception that forces the user to read the JVM internal error messages to realise that he misused the api.
Since it's relatively frequented message I was wondering if it wouldn't be better to pass the path to the disl-bypass.jar as another parameter to the agent and then add the path as the bootstrap classloader segment using the AddToBootstrapClassloaderSearch JVMTI method after we explicitly check whether the specified file exists.
It's not really must-have feature, but it would increase the user experience a bit.