method handler crashed error for prestateTracer #2066
Comments
quick-pawiromitchel
added
triage
|
@quick-pawiromitchel Thanks for reporting this. I could reproduce it. The stacktrace is: |
|
@quick-pawiromitchel Just to clarify, besides the crash which shouldn't happen, what outcome did you expect? The example you provided sends a normal transaction without code, so the tracer's So now I wonder if this is an existing bug in the prestate tracer (that may have been fixed upstream in the meantime). |
|
@quick-pawiromitchel thanks for submitting the issue! got response Please let me know if something else is needed from my side to troubleshoot that. |
|
@quick-pawiromitchel @mikhail-hiryliuk Note that the diff mode has been added more recently, so we don't include it yet. |
|
I tested this again and #2075 fixes this problem. The difference in error messages stems from the different versions. $ http 127.0.0.1:8545 jsonrpc=2.0 id=0 method=debug_traceCall params:='[{"from": "0x61640A8D48Bca205BA91b16B0B7745e7aBc61084","to": "0xe75b0bc5dda1cbbac7075de5b1a39e9755938648","value": "0x5af3107a4000"},"latest",{"tracer": "prestateTracer"}]'
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 101
Content-Type: application/json
Date: Thu, 27 Apr 2023 08:57:11 GMT
{
"error": {
"code": -32000,
"message": "method handler crashed"
},
"id": "0",
"jsonrpc": "2.0"
}
$ http 127.0.0.1:8545 jsonrpc=2.0 id=0 method=debug_traceCall params:='[{"from": "0x61640A8D48Bca205BA91b16B0B7745e7aBc61084","to": "0xe75b0bc5dda1cbbac7075de5b1a39e9755938648","value": "0x5af3107a4000"},"latest",{"tracer": "prestateTracer"}]'
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 177
Content-Type: application/json
Date: Thu, 27 Apr 2023 08:58:09 GMT
{
"error": {
"code": -32000,
"message": "TypeError: cannot read property '0x61640a8d48bca205ba91b16b0b7745...' of null in server-side tracer function 'result'"
},
"id": "0",
"jsonrpc": "2.0"
}And with #2075 we get the trace: $ http 127.0.0.1:8545 jsonrpc=2.0 id=0 method=debug_traceCall params:='[{"from": "0x61640A8D48Bca205BA91b16B0B7745e7aBc61084","to": "0xe75b0bc5dda1cbbac7075de5b1a39e9755938648","value": "0x5af3107a4000"},"latest",{"tracer": "prestateTracer"}]'
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Length: 182
Content-Type: application/json
Date: Thu, 27 Apr 2023 08:59:06 GMT
{
"id": "0",
"jsonrpc": "2.0",
"result": {
"0x61640a8d48bca205ba91b16b0b7745e7abc61084": {
"balance": "0x7cb35c62f0ad5619",
"code": "0x",
"nonce": 16,
"storage": {}
},
"0xe75b0bc5dda1cbbac7075de5b1a39e9755938648": {
"balance": "0x0",
"code": "0x",
"nonce": 0,
"storage": {}
}
}
} |
|
@palango thanks for fixing the issue with error response! |
@mikhail-hiryliuk Not that I'm aware unfortunately. However, once the PR that merges native (call)tracing is merged is should be relatively simple to merge the native prestate tracer with the diff mode feature. |
Expected Behavior
I expect a non
-32000responseActual Behavior
Steps to reproduce the behavior
When replacing the
prestateTracerwithcallTracer, it works fineBacktrace
System Information
Client version:
celo/v1.7.3-stable-6efea76c/linux-amd64/go1.20.2Chain/Network:
MainnetThe text was updated successfully, but these errors were encountered: