[Soot-list] Use Parameter to decrease memory consumption in eclipse

Steven Arzt Steven.Arzt at cased.de
Tue Apr 14 04:34:02 EDT 2015


Hi Stefan,

I think you are referring to FlowDroid and not a custom analysis, right? Otherwise, these options do not make much sense since they are not generic Soot options.

1) If you programmatically use FlowDroid, you have setters with which you can configure the "Infoflow" class (or the "SetupApplication" class respectively).
2) The "aliasflowins" option make the alias analysis flow-insensitive, i.e. we do not take the order of statements into account. This is less precise as you can have a "leak" on an alias that hasn't been created yet because it only comes later in the code. However, it also requires us to store fewer different things in memory. It's a tradeoff whether this increases the runtime due to tracking invalid aliases or whether it decreases it due to the less complex and time-consuming alias analysis.

Best regards,
  Steven

-----Ursprüngliche Nachricht-----
Von: soot-list-bounces at CS.McGill.CA [mailto:soot-list-bounces at CS.McGill.CA] Im Auftrag von Stefan Gommer
Gesendet: Dienstag, 14. April 2015 10:21
An: soot-list at CS.McGill.CA
Betreff: [Soot-list] Use Parameter to decrease memory consumption in eclipse

Hi, 

my analysis uses too much memory so I’m always getting the gc overhead limit exceeded exception. There are these parameters like aplength or nopaths to change memory consumption for preciseness. I have to two questions about them:

1) How can I use them in my own application in eclipse?

2) what exactly does —aliasflowins? Is it some kind of pointer analysis because it seems to be very expensive


Regards,

Stefan
_______________________________________________
Soot-list mailing list
Soot-list at CS.McGill.CA
https://mailman.CS.McGill.CA/mailman/listinfo/soot-list



More information about the Soot-list mailing list