[Soot-list] Bug in TopologicalOrderer

[Eric Bodden]

Hi Michael.

Sorry I think I don't understand the problem.

Could you please rephrase or give an example?

Eric

On 9 March 2013 12:00, Michael Faes <rolve at trick17.ch> wrote:
> (Sorry, here is the rest:)
>
>      public void go() {
>          Iterator methods = cg.sourceMethods();
>          while( methods.hasNext() ) {
>              SootMethod m = (SootMethod) methods.next();
>              dfsVisit( m );
>          }
>      }
>
> As you can see, only methods that have at least one outgoing edge are
> visited, and (not visible here) of course those reachable by such
> methods. However, *all* reachable methods should be taken into account.
>
> Best regards,
> Michael
>
> -------- Original-Nachricht --------
> Betreff: Bug in TopologicalOrderer
> Von: Michael Faes <rolve at trick17.ch>
> An: Soot list <soot-list at sable.mcgill.ca>
> Datum: 09.03.2013 11:56
>
>> Dear Sooters,
>>
>> I think I found a bug in
>> soot.jimple.toolkits.callgraph.TopologicalOrderer. It does not consider
>> reachable, but unconnected methods. Obviously, methods can only be both
>> if we have custom entry points.
>>
>> Here is the problematic code:
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list



-- 
Eric Bodden, Ph.D., http://sse.ec-spride.de/ http://bodden.de/
Head of Secure Software Engineering Group at EC SPRIDE
Tel: +49 6151 16-75422    Fax: +49 6151 16-72051
Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt