[Soot-list] Soot-list Digest, Vol 112, Issue 1

[Manas Thakur]

Thanks Julien. Examples helped.

- Manas


On Fri, Aug 1, 2014 at 9:30 PM, <soot-list-request at cs.mcgill.ca> wrote:

> Send Soot-list mailing list submissions to
>         soot-list at CS.McGill.CA
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
> or, via email, send a message with subject or body 'help' to
>         soot-list-request at CS.McGill.CA
>
> You can reach the person managing the list at
>         soot-list-owner at CS.McGill.CA
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Soot-list digest..."
>
>
> Today's Topics:
>
>    1. Finding path conditions in Soot (Manas Thakur)
>    2. Re: Finding path conditions in Soot (Julien Klaus)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 1 Aug 2014 15:50:42 +0530
> From: Manas Thakur <manasthakur17 at gmail.com>
> Subject: [Soot-list] Finding path conditions in Soot
> To: soot-list at cs.mcgill.ca
> Message-ID:
>         <
> CAOChv7EpGG0S02cBFMH9TUvBszP8OVF-NJwf_ZGoqvf9z+ucqg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I have been trying to find a series of conditions under which a path
> executes. I could find a post in this mailing list from 2012, which says it
> is possible with ForwardBranchedFlowAnalysis. Still I am not clear with how
> can the conditions be propagated and aggregated for goto's and if's
> generated as a result of various programming constructs.
> Can someone describe the specific details, or provide a link to some
> paper/code-snippet where conditions are propagated through the various
> paths of a program in Soot?
>
> Thanks and regards,
> Manas
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20140801/9a7a1157/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Fri, 01 Aug 2014 15:41:02 +0200
> From: Julien Klaus <julien.klaus at uni-jena.de>
> Subject: Re: [Soot-list] Finding path conditions in Soot
> To: soot-list at CS.McGill.CA
> Message-ID: <53DB98EE.4010200 at uni-jena.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello Manas,
>
> you can get the conditions from a unit of the JIfStmt class with the
> method getCondition()
> (http://www.sable.mcgill.ca/soot/doc/soot/jimple/internal/JIfStmt.html).
> Also you can it propagate with the help of a graph. You can use the
> UnitGraph
> (http://www.sable.mcgill.ca/soot/doc/soot/toolkits/graph/UnitGraph.html).
> With
> the methods getPredsOf(Unit u) or get getSuccsOf(Unit u) you can
> coordinate through the graph of your programm. When you use the
> ForwardBranchedFlowAnalysis you can use the UnitGraph in the method
> doAnalysis(). When you look in the documentation of
> ForwardBranchedFlowAnalysis
> (
> http://www.sable.mcgill.ca/soot/doc/soot/toolkits/scalar/ForwardBranchedFlowAnalysis.html
> )
> you find some classes which extended this class. Maybe the source code
> or this presentation
> (http://www.iro.umontreal.ca/~dufour/cours/ift6315/docs/soot-tutorial.pdf)
> helps.
>
> Regards,
> Julien
>
> Am 01.08.2014 12:20, schrieb Manas Thakur:
> > I have been trying to find a series of conditions under which a path
> > executes. I could find a post in this mailing list from 2012, which
> > says it is possible with ForwardBranchedFlowAnalysis. Still I am not
> > clear with how can the conditions be propagated and aggregated for
> > goto's and if's generated as a result of various programming constructs.
> > Can someone describe the specific details, or provide a link to some
> > paper/code-snippet where conditions are propagated through the various
> > paths of a program in Soot?
> >
> > Thanks and regards,
> > Manas
> >
> >
> > _______________________________________________
> > Soot-list mailing list
> > Soot-list at CS.McGill.CA
> > https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20140801/e2321849/attachment-0001.html
>
> ------------------------------
>
> _______________________________________________
> Soot-list mailing list
> Soot-list at CS.McGill.CA
> https://mailman.CS.McGill.CA/mailman/listinfo/soot-list
>
>
> End of Soot-list Digest, Vol 112, Issue 1
> ****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.CS.McGill.CA/pipermail/soot-list/attachments/20140802/00c7b9e6/attachment.html