Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve runtime debug output for contract-to-contract calls #762

Open
MetaB0y opened this issue Aug 11, 2022 · 0 comments
Open

Improve runtime debug output for contract-to-contract calls #762

MetaB0y opened this issue Aug 11, 2022 · 0 comments

Comments

@MetaB0y
Copy link

MetaB0y commented Aug 11, 2022

Is your feature request related to a problem? Please describe.

I am working on an app which features contract-to-contract calls. I have contract A and contract B. B calls A using inner transactions. When I am executing it with Algobuilder runtime debugger (runtime.executeTx(myTxs, 2)), it runs fine but after A calls B, it continues to output as if nothing happened.

An example:

stack(depth = 2) for opcode ITxnField at line 619:
stack(depth = 2) for opcode Retsub at line 620:
stack(depth = 2) for opcode Pragma at line 1:
stack(depth = 2) for opcode Txn at line 2:

Here, the first two lines belong to contract A, but the last two lines belong to contract B.

Describe the solution you'd like

I would like the debugger to output something ---CALLING CONTRACT A--- and ---BACK TO CONTRACT B--- between the switches as the minimum.

Some possible improvements/options could be writing the name of the running contract on each line and using indentation to show call depth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant