Skip to content
This repository has been archived by the owner on Oct 28, 2021. It is now read-only.

performing null rpc request causes crash (exception thrown) #3184

Open
bobsummerwill opened this issue Aug 26, 2016 · 3 comments
Open

performing null rpc request causes crash (exception thrown) #3184

bobsummerwill opened this issue Aug 26, 2016 · 3 comments
Assignees

Comments

@bobsummerwill
Copy link
Contributor

From @subtly on July 4, 2016 6:43

Behavior: Calling eth_getStorageAt with "0x" as address causes crash.
Expected: Invalid input should result in an error log not crash the client.

Copied from original issue: ethereum/webthree-umbrella#611

@bobsummerwill
Copy link
Contributor Author

Thanks for the report, @subtly.

@bobsummerwill
Copy link
Contributor Author

From @winsvega on July 6, 2016 15:56

Can't reproduce.
My request:
"{"jsonrpc":"2.0","method":"eth_getStorageAt","params":["0x", "0x", "0"],"id":7}"
Reply:
"{"error":{"code":-32602,"message":"INVALID_PARAMS: Invalid method parameters (invalid name and/or ty"... (140)

what eth node configuration, chain status did you use?

@chfast
Copy link
Member

chfast commented Jan 25, 2017

@winsvega or @yann300 please recheck it.

@axic axic added the rpc label Jan 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants