Debugging solidity on-chain could be more tricky than you thought, debugger results sometimes show missing function calls, or show unexpected parameter values, weird execution order, or mismatched source code. This is largely due to solidities compiler optimization. e.g. function inline, function specializer, etc.
Sentio lets you choose different build modes of the solidity binary on chain to overcome the problem.
Debug build essentially replaces the binary with the one that doesn't use optimization and makes the execution flow very clean.
However in this case, it uses more gas, so you may see out of gas error, or if some contract is use gas to do some checking, it may not work well.
Debug Build without Gas
Similar to the debug build, except gas usage is ignored.
This solves out of gas issue in normal debug build, but noted this may cause different code execution. e.g. if the original transaction is out of gas, using debug build will make the transaction fully executed.
You could try this example and switch it's build mode, you will see the trace is different:
The debug build will reflect the logic code flow more accurately while the release build reflect the more real execution order after inline optimization.