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
There is a problem with kAFL's status update. When a node is displayed as STALLED, CurExec still calculates it. As shown in the figure, the status of worker 1 2 3 is displayed as STALLED. CurExec should be the value of worker 0, not the fixed value of worker 1 2 3 plus the current value of worker 0.
The text was updated successfully, but these errors were encountered:
At the same time, I also want to understand why the STALLED situation occurs. Does kAFL have some native options, such as timeout settings, to avoid or rescue the worker from the STALLED state?
Below is the backtrace of a STALLED worker.
There is a problem with kAFL's status update. When a node is displayed as STALLED, CurExec still calculates it. As shown in the figure, the status of worker 1 2 3 is displayed as STALLED. CurExec should be the value of worker 0, not the fixed value of worker 1 2 3 plus the current value of worker 0.
The text was updated successfully, but these errors were encountered: