You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging a TEAL program, given an error message from a Application Call, there is no straightforward way to map the PC returned in the error message to the line of TEAL.
Solution
We could append the PC to each line during disassembly by default or given an appropriate flag.
Alternatively, during assembly, we could output a JSON file with these details and any other details about the program. Other details might include program cost or some details about Template Variables or hash of the contract.
Dependencies
Probably the assembler and maybe an ARC or spec addition?
The text was updated successfully, but these errors were encountered:
Problem
When debugging a TEAL program, given an error message from a Application Call, there is no straightforward way to map the PC returned in the error message to the line of TEAL.
Solution
We could append the PC to each line during disassembly by default or given an appropriate flag.
Alternatively, during assembly, we could output a JSON file with these details and any other details about the program. Other details might include program cost or some details about Template Variables or hash of the contract.
Dependencies
Probably the assembler and maybe an ARC or spec addition?
The text was updated successfully, but these errors were encountered: