Fetching internal transaction result is incorrect

[zhen6939]

I used Parity's trace RPC api to fetch internal transaction.
the response contained an "out of gas" call. However, I double checked the transaction on etherscan, it was successful.

request:

curl --data '{"method":"trace_transaction","params":["0x807384a74b907d826450007877f849482e2df077461f67001893378fe6460d4f"],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545

response:

{
"action": {
"callType": "call",
"from": "0x60bf91ac87fee5a78c28f7b67701fbcfa79c18ec",
"gas": "0x3",
"input": "0x",
"to": "0x0000000000000000000000000000000000000004",
"value": "0x0"
},
"blockHash": "0xad5cfde183cd9a4d0f98004860068d0e976cf439b36b00c20802647c8a7d60b2",
"blockNumber": 4017014,
"error": "Out of gas",
"subtraces": 0,
"traceAddress": [
0,
0,
0,
0,
0,
1
],
"transactionHash": "0x807384a74b907d826450007877f849482e2df077461f67001893378fe6460d4f",
"transactionPosition": 22,
"type": "call"
}

When I checked etherscan:

https://etherscan.io/tx/0x807384a74b907d826450007877f849482e2df077461f67001893378fe6460d4f

The transaction succeed.

[stephenjudkins]

We've also seen this. Here's an example TX showing this issue: https://etherscan.io/vmtrace?txhash=0xe3c884a2bc63e033ab3110a8bb50156f81e50c72bc329b1471a1aadedeff3850&type=parity

[lastperson]

This is an old solidity compiler bug ethereum/solidity#827 . Mentioned contract was deployed 2 weeks before the bug was fixed. There is indeed out of gas internal call, though it doesn't affect the execution, parity reports correctly on this one.