User loginNavigationWho's online
There are currently 0 users and 0 guests online.

Why does Lancet shows unconnected graphs for some control flow graphs?When Lancet displays the control flow graph of a function, it sometimes occurs that the graph is not connected.
Escaping edge (i.e. edges that jump or fall through to another function) occur quite often in library code. In diablo, we cannot easily determine to which functions a basic block actually belongs and we use some algorithm to delimit the boundary of functions. This can introduce some extra escaping edges. To make it worse, there is another algorithm that turns all functions found by the previous step into 'single entry' functions, where there is only one basic block with forward incoming interprocedural edges. This algorithm introduces even more escaping edges. It also splits some functions into several parts. Those parts get the name of the function they originally belonged to, but suffixed with a number (like in this case _IO_vfprintf_5).
