Carlos Galindo
Carlos Galindo
Hi there! The `UnsolvedSymbolException` is related to missing some classes in part of the analysis. I'd suggest including the libraries' source code with `-i ` or the jars in the...
Hi @diohabara, I can confirm the bug locally. I have had some problems with the symbol solver we're using, to the point of having forked it and placed it as...
We're currently working on it, it worked in previous versions but doesn't work right know. See #47 for more details.
We're currently in the process of adding OO features to the slicer, and static fields are far down the list. I'm afraid this slicer still has at least a month...
CLI side of issue replaced by #27. Updating title and description.
This is a known issue, the slicer is missing a points-to analysis, to determine which variables (may) point to the same object, and thus be considered a dependency. The basic...
@bystc I'm glad you're using the slicer, and although the issue reports are very informative, I'm not going to be able to address them one by one. Each change can...
Currently, body-less methods are not supported. `abstract` methods could be supported in the future, but they bring with them the possibility that some calls to user-provided code do not have...
This is a bug in the chain of data and object dependencies. For a workaround, you can slice with respect to `obj`, and that will include the nested elements. I'll...
This is part of a larger issue, which is that the slicer knows nothing about the methods called in the source code (unless it also parses the source code for...