Handling null initializations

[asoifer]

Hi again,
I think that I'll be your main slicer tester.
This is because I'm working on my own dynamic slicer and I'm performing several tests.

In this case, I'll use the same case as before, TreeAdd.
I developed a comparer for helping me to characterize the difference between different slicers.

I'm slicing from line 53 in TreeAdd.java with the same parameters as before "-l 2".

In this picture, lines from 101 to 106 are in the slice, and this is OK!

But in this picture, lines 54 and 55 are not in the slice.
At the left is my slicer, in the middle Javaslicer, in the right Slcier4j (I used the same for comparing to ORBS).

Probably, I guess, this is because the compiler omits those lines (since null values are the default ones...).
I don't know if this is easy or not to solve,

Anyway, I'll upload more "issues" as soon, I hope the best for this tool,
And if you need some help I can help :)
Regards.

[asoifer]

I'm sorry,
I've seen that you don't really need those lines... since you don't execute the body in that conditions.
I have other cases, but in this case the tool is ok!

[khaled-e-a]

Thank you for testing Slicer4J, really appreciate it! Looking forward for the other issues :)
Are you using a some program to automatically highlight the slices? This highlighting looks cool and would be awesome to have in Slicer4J

[asoifer]

Yes, I developed some programs for running, processing, and understanding the slices.
Lets talk by email,
See u!