[Soot-list] Problems with LoopFinder

[Eric Bodden]

Kelvin did you look at the Jimple code? It could well be that this
method does have three possible loops, due to the exceptional flow.

Eric

2009/9/28 Kelvin Tian <kevinn.tian at gmail.com>:
> Hi,
>
>   I'm not sure whether this is a possible bug with LoopFinder, but when I
> tried to use LoopFinder to find loops in jvm benchmarks. I found some loops
> are identified by soot for more than one times.  One typical loop is like
> below.  I just compile it, and use LoopFinder to identify the loops.
> Although there's only one loop in main(), LoopFinder identifies three loops,
> which all point to the same location.  This seems very strange to me, and I
> couldn't figure out what's the possible reason.  Thanks for any suggestions!
>
>
> ======================
> import java.io.*;
>
> class Test2 {
>
>     public static void main(String args[]){
>
>              int numObj = 0, ObjID = 0;
>
>              try {
>                     DataInputStream infile = new DataInputStream(new
> FileInputStream("test"));
>
>                     String input;
>
>                     while ((input = infile.readLine()) != null) {
>
>                             if (input.equals("camera {"))
>                                     numObj++;
>                             else if (input.equals("point_light {"))
>                                     ObjID++;
>                     }
>                     infile.close();
>              } catch (Exception e) {
>                     System.err.print("IO Error!\n");
>              }
>
>     }
>
> }
>
>
> --
> Best regards,
> Kelvin
>
>
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
>



-- 
Eric Bodden
Software Technology Group, Technische Universität Darmstadt, Germany
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt