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
When tracing is enabled, however, there is one single fail, which can be reproduced using the following command with master df9c73c; it causes t8n to exit with SIGSEGV (more context regarding the test case below):
which implements a blockchain test with two blocks:
In the first block a withdrawal is made to the precompile address 0x09.
In the second block a no-value transaction is sent to the precompile address 0x09.
This test is parametrized by precompile address and, interestingly, the error is not triggered for other precompile addresses, i.e., the following tests all run without problem:
I'm currently adding nimbus
t8n
tool support to ethereum/execution-spec-tests, cf ethereum/execution-spec-tests#229. All test cases (valid until Shanghai) execute correctly with tracing disabled.When tracing is enabled, however, there is one single fail, which can be reproduced using the following command with master df9c73c; it causes
t8n
to exit withSIGSEGV
(more context regarding the test case below):Resulting backtrace:
If the
--trace
option is not specified,t8n
generates the expected output on stdout.Test Case Context
The
t8n
command above is executed as part of the withdrawal test case, tests/shanghai/eip4895_withdrawals/test_withdrawals.py#L727:which implements a blockchain test with two blocks:
This test is parametrized by precompile address and, interestingly, the error is not triggered for other precompile addresses, i.e., the following tests all run without problem:
only the following two cases involving the 0x09 precompile trigger the issue:
These test cases can be executed with:
The text was updated successfully, but these errors were encountered: