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
Recent initial attempts to introduce fuzzing to the portfolio of our test infrastructure has revealed an issue in LFVM's implementation of the LOG operations. The issue has been fixed by #541.
It would be interesting to understand why this issue was not detected by the CT infrastructure - and if possible this issue should be fixed. Furthermore, if it is an example for a general class of issues, the CT test case generation process may be improved to cover those types of issues for a wider range of situations.
The text was updated successfully, but these errors were encountered:
While looking into increasing lfvm coverage I came upon a similar issue, where a branch was not reached because of the combination of parameters between Gas samples and MemoryOffset sizes would always exit with not enough gas, before even trying to ensure capacity. An attempted fix is presented in #564
Recent initial attempts to introduce fuzzing to the portfolio of our test infrastructure has revealed an issue in LFVM's implementation of the LOG operations. The issue has been fixed by #541.
It would be interesting to understand why this issue was not detected by the CT infrastructure - and if possible this issue should be fixed. Furthermore, if it is an example for a general class of issues, the CT test case generation process may be improved to cover those types of issues for a wider range of situations.
The text was updated successfully, but these errors were encountered: