rpc: excessive gasCost value for CALL opcode

[Sixtysixter]

System information

Erigon version: erigon version 3.01.0-dev-54548aca

OS & Version: Windows/Linux/OSX: ubuntu

Commit hash: 54548ac

Expected behaviour

CALL gasCost value consistent with the other cases

Actual behaviour

CALL gasCost seems to be excessive

Steps to reproduce the behaviour

Invove the following API:

{
  "jsonrpc":"2.0",
  "method":"debug_traceTransaction",
  "params":[
     "0x1c19a6e5089ff08b39144162f105f2d5519268f5360dab733d1b4f029503fdbe",
     {"disableStorage": true,"disableMemory": true,"disableStack": true}
  ],
  "id":1
}

Backtrace

The resulting JSON reports an incorrect gasCost value for the CALL operation at PC: 3930.

{
  "depth": 2,
  "error": "out of gas",
  "gas": 2795,
  "gasCost": 18158513697557842775,
  "op": "CALL",
  "pc": 3930
}

The complete JSON is attached.

test_134-rpcdaemon.json

[backtrace]

[yperbasis]

@Giulio2002 don't think it's that urgent to fix because it's about misreporting gasCost when out of gas

[Giulio2002]

@Giulio2002 don't think it's that urgent to fix because it's about misreporting gasCost when out of gas

not a blocker but it might be enough for some people not to switch over because it is an API mismatch

also this does not look a huge one as we can already detect the out of gas case

[VBulikov]

yperbasis changed Importance from Imp2 to Imp1

[yperbasis]

It's the same in e2, so shouldn't be a blocker for e3.

[VBulikov]

yperbasis changed Importance from Imp1 to Imp2

[yperbasis]

Here's output from Nethermind for reference:

debug_traceTransaction.json