Sometimes in a large contract, in a message chain A -> B -> C -> D, with Tact compiler debug mode on, execution would stop at C, and the message C->D would not be sent (there's enough incoming gas). When adding some dumps in the code in contract C trying to debug the issue (with no other functional code changes), the entire chain would succeed and C->D is correctly sent. If I disable debug mode, execution would also stop at C.
Sometimes in a large contract, in a message chain A -> B -> C -> D, with Tact compiler debug mode on, execution would stop at C, and the message C->D would not be sent (there's enough incoming gas). When adding some
dumps
in the code in contract C trying to debug the issue (with no other functional code changes), the entire chain would succeed and C->D is correctly sent. If I disable debug mode, execution would also stop at C.Any ideas why this could happen?
Tact 1.3.0