[Soot-list] Memory problems in whole-program-mode

[Michael Pradel]

Thanks! I get a call graph by changing the settings.

If there's a way to build the call graph of only parts of the
application, I'd still be interested, though.


Michael


saswat at gatech.edu wrote:
> There are two options that I think may help to some extent. They
> do not prevent building of callgraph of library code, but they
> reduce the precision other ways and thus should improve scalability.
> 
> Change the default settings for both. 
> 
> Types For Sites (types-for-sites)
>     (default value: false)
>     When this option is set to true, types rather than allocation 
> sites are used as the elements of the points-to sets. 
> 
> Implicit Entry Points (implicit-entry)
>     (default value: true)
> 
>     When this option is true, methods that are called implicitly 
> by the VM are considered entry points of the call graph. When it 
> is false, these methods are not considered entry points, leading 
> to a possibly incomplete call graph. 
> 
> Saswat
> 
> 

-- 
michael at binaervarianz.de
GPG Fingerprint 2069 ED1D 7A80 E35E F4C9  43CF D4E0 57FC 7B97 6D4F

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
Url : http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20090819/98805c13/attachment.bin