New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code instumentation errors #16
Comments
This is a soot issue, fixed by updating to the latest soot build. I can now create the instrumented JAR. Please pull and re-build both DynamicSlicingCore and this repo. |
Thank you for the fix but unfortunately I get another problem when instrumenting the Jar. This is the output of EDIT: I just saw, I actually do get an instrumented jar, despite the error. I nevertheless want to report the error
I pulled, cleaned and re-built both, Core and Slicer4J |
I do not get this error, however, it seems like disabling soot's unreachable code optimization may work. I'll try that and update the code and let you know. |
Hi there, I got another problem with Jar instrumentation.
I tried to slice test cases from javapoet and I got the following error message in
instr-debug.log
:Here's the fat jar I created from the project:
javapoet-1.14.0-SNAPSHOT-fat-tests.zip
This is not the first time that I am seeing issues related to
SymbolTable
. When I was trying to perform slicing on thecommons-lang
library I got similar errors during instrumentation. This is really a problem because I need to benchmark at least 10 projects for my Master's thesis and so far Slicer4J managed to work with 3 of over 20 open source projects I tried.I would be really happy if you could look into this issue. Thank you.
The text was updated successfully, but these errors were encountered: