How to traverse the StmtGraph of a Body avoiding infinite loops?

[topcoco]

What happened?

When I use stmtGraph to traverse a method that contains loops, such as while or nested loops, it leads to infinite recursion, causing the analysis to crash. Is there a way to handle methods with such loop structures properly?

Version

Latest develop branch

Relevant log output

Exception in thread "main" java.lang.StackOverflowError
	at kotlin.text.StringsKt__StringsJVMKt.replace(StringsJVM.kt:88)
	at kotlin.text.StringsKt__StringsJVMKt.replace$default(StringsJVM.kt:85)

[swissiety]

Hi,
how did you print the Jimple code? From what I see there is no return stmt in the last mage - which is weird.
On the other hand from your description it seems that your implementation does not check if a stmt is already visited?
Maybe you can make use of an Iterator e.g. BlockStmtGraphIterator

[topcoco]

This is how I get the method of Jimple

[topcoco]

另一方面，从您的描述来看，您的实现似乎没有检查是否已访问过 stmt？
也许你可以使用一个 Iterator，例如BlockStmtGraphIterator
How exactly to deal with this kind of loop, that's how I'm doing it now, I'm really sorry, I'm a novice to the framework of the sootup class

[swissiety]

a) The Jimple makes sense as this is an infinite loop and a BodyInterceptor (ConditionalBranchFolder) that is executed by default removed the return Stmt. @kadirayk @stschott Maybe we should add a configuration option to that BodyInterceptor to not remove the only return Stmt, even if it is never reached?

b) your code: as we are in a loop and you are traversing the first successors of each Stmt the JGotoStmt points to an already visited Stmt (a backwards edge if we speak in graph theorie terms) which means you have to manage a collection of already visited Stmts or you use the provided iterator of the StmtGraph to iterate them like we would serialize the Stmt to a human readable, linear output of the Stmts (like the Jimple Code you shared) - depending what you want to achieve.