[Soot-list] Re : Spark and aliasing analysis

[Florian Strauß]

Thanks for your answer.
Okay, in the second example is only one "new Object()" statement, therefore
there is only one allocation node representing this statement. Hence, the
pointsTo-sets contain the same node.
Conclusion: No way to do this with spark, right?
What's about Paddle? Would Paddle return different pointsTo-sets?  

Best regards,
	Florian



-----Ursprüngliche Nachricht-----
Von: soot-list-bounces at sable.mcgill.ca
[mailto:soot-list-bounces at sable.mcgill.ca] Im Auftrag von Quentin Sabah
Gesendet: Mittwoch, 9. Mai 2012 14:36
An: Florian Strauß
Cc: soot-list at sable.mcgill.ca
Betreff: [Soot-list] Re : Spark and aliasing analysis

Hi Florian,

In your first exemple, each variable is assigned to a different allocation
node since there are two distinct "new" expressions.
But in your second exemple, o7 and o8 both have at least in common the
allocation node found in getNewO().

> Object o7 = k1.getNewO();
> 
> Object o8 = k2.getNewO();
> 
> //In class ClassA:
> 
> public Object getNewO() {
> 
>    return new Object();
> 
> }
> 
>  
> 
> But in this case, the framework says that the two pointsTo-Sets (of o7 and
> o8) has an non empty intersection. 


-- 
Quentin Sabah, co-funded Ph.D. student
Grenoble University
INRIA-SARDES                   | STMicroelectronics/AST
Montbonnot, France             | Grenoble, France
mailto:quentin.sabah at inria.fr  | mailto:quentin.sabah at st.com
phone: +33 476 61 52 42        | phone: +33 476 58 44 14
_______________________________________________
Soot-list mailing list
Soot-list at sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list