[Soot-list] simple context-sensitive call graph

[Ondrej Lhotak]

Hello Khilan...

Paddle does not have to use call strings: it was designed to be very
customizable in the context abstraction that it uses. Changing the
context abstraction requires only implementing new subclasses of
AbsStaticContextManager and AbsVirtualContextManager. These classes
should be very simple and short. Dan Grossman did almost exactly what
you are suggesting, but with atomic blocks rather than synchronized
blocks, and he said it went very well. See his PLDI 2007 paper
titled "Enforcing isolation and ordering in STM".

Ondrej

On Thu, Oct 01, 2009 at 09:07:53PM +0100, Khilan Gudka wrote:
> Hi,
> 
> How hard would it be to create a context-sensitive call graph, which  
> had only two contexts A and B. The contexts refer to whether the edges  
> are due to objects allocated outside a synchronized block and edges  
> which are due to objects allocated inside a synchronized block. I do  
> not wish to use Paddle because it uses callstrings. I don't need  
> callstrings, just two contexts.
> 
> --
> Khilan Gudka
> PhD Student
> Department of Computing
> Imperial College London
> http://www.doc.ic.ac.uk/~khilan/
> 
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>