Detect out-of-gas in debugger to improve error messages

[gnidan]

Since we know how much gas is left, we should be able to deduce that we're out of gas, instead of the current message:

There was no revert message. This may be due to an in intentional halting expression, such as assert(), revert(), or require(), or could be due to an unintentional exception such as out-of-gas exceptions.
Please inspect your transaction parameters and contract code to determine the meaning of this error.

If we use trace.step's gasCost and gas, we might be able to provide a higher degree of certainty for out-of-gas errors.

[haltman-at]

Hm, do we know that gasCost is reliable? I'd want to check that out before implementing this. If it is then I guess this should be fine.

There's also the question of whether this is only checked at end of transaction or on any revert. I suppose we'd have to do the latter if we want to to work it with the stacktraces, but that's not too bad; we cam just store that info.

Notionally we could expand this system to other low-level reasons, but that probably isn't worth it because people care about the high-level reasons, not the low-level reasons, and that would be a lot harder (and low-level reasons other than out of gas, invalid instruction, and REVERT aren't that likely to come up in a contract compiled from a higher-level language like Solidity).

[haltman-at]

Oh yeah I guess gasCost is reliable, I think I was confusing it with something else that's unreliable.

Edit: Disregard that, it's not. Hm. I don't know how to do this, then.

[laki016]

How can i get my smart contract and how to solve this problem?I was left without my tokens and without 0.068eth.

[haltman-at]

@laki016 Your comment does not seem related to this issue? If you are having a Truffle issue, I would suggest filing a new issue report. Thank you!