Known issues and limitations

These are items we want to let you know about:

• Incomplete support of OSSI for Windows 10 version 21H1 VMs: The OSSI cannot find the ntoskrnl.exe binary in Windows 10 version 21H1 scenarios. This has the following consequences for these scenarios:

  • All portions of the trace executing the ntoskrnl.exe binary report an unknown location to Axion and the API.
  • WinDbg interoperability does not work on these scenarios.
  • Scripts that make use of ntoskrnl.exe (such as data_race_detection.ipynb) will not work on these scenarios.

• The Axion layout is not fully saved: When restarting Axion, changes made to the size of the left and right columns of widgets may not be saved after updating Axion. If this happens to you, then remove the $HOME/.config/tetrane/reven2.conf file. The layout will be reset to the default on the next Axion startup, but it will be saved as expected for future launches of Axion.

• In case Axion is unresponsive on some scenarios, try to delete the strings resource and restart the REVEN server on this scenario.

• Only a single taint can run concurrently per REVEN scenario: currently, starting a second taint, even from a different Axion or the Python API, will cancel the first running taint. Besides, if two clients (such as two Axion sessions) are involved, the first client may display mixed taint results.

• If a taint generates many changes, the taint widget may slow down Axion. Cancelling the current taint operation will revert Axion's slowdown.

• When using the auto-record functionality, the replay operation may fail at the start of the trace with the following error: detect_infinite_loops: Assertion 'false' failed. Performing a new scenario recording usually fixes the issue.