"message": "unrecognized call frame type: STOP" on debug_* using flatCallTracer

[yaanakbr]

Describe the bug

Users are reporting errors unrecognized call frame type: STOP using debug_traceBlockByNumber

To Reproduce

{  
    "method": "debug_traceBlockByNumber",                                   
    "params": [
        "0xC10D988",
        {
            "tracer": "flatCallTracer"
        }
    ],
    "id": 0,
    "jsonrpc": "2.0"
  }
  

Is returning

{
    "jsonrpc": "2.0",
    "id": 0,
    "error": {
        "code": -32000,
        "message": "unrecognized call frame type: STOP"
    }
}

Additional context

I test all our nodes, and this error message is applicable on all of them. One thing to note is that this does work with callTracer

There is no panic on our end;

Jun 13 18:16:05  nitro[17016]: WARN [06-13|18:16:05.067] Served debug_traceBlockByNumber          conn=127.0.0.1:31652 reqid=0 duration=14.694899ms err="unrecognized call frame type: STOP"

[quickchase]

Related: ethereum-optimism/op-geth#248

[joshuacolvin0]

Fixed by #2402 which will be in next release

[Tristan-Wilson]

The fix is present in the v3.0.2 release https://github.com/OffchainLabs/nitro/releases/tag/v3.0.2