You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've noticed that having a sink in the sources set changes the outcome of reachableBy in unexpected ways. Below are three test cases showing this behaviour.
@xavierpinho, from what I understand, there is a mechanism in the data-flow engine where the shortest path is returned if found, but also a path length ≤ 1 is filtered out - these might be running in an order where flows disappear.
We've noticed that having a sink in the sources set changes the outcome of
reachableBy
in unexpected ways. Below are three test cases showing this behaviour.Joern version: 4.0.131
Test case 1 ✅
Source is
literals
, and works as expected.Test case 2 ✅
Source is
sink
, and works as expected.Test case 3 ❌
Source is
literals
plussinks
, and misses the result from Test case 1. That is, this test case's outcome is the same as that of Test case 2.The expected behaviour would be for Test case 3 to output 2 results, namely those from Test case 1 and 2.
The text was updated successfully, but these errors were encountered: