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
Even if writing zephyr programs is quite simple and writing code that's formally incorrect is difficult, when that happens debugging is currently very difficult. Not to mention that some soroban host functionalities are not yet supported and when used will inevitably result in SVM errors that are not debuggable client-side.
To improve this we should carry host-side stack traces about potential raised errors. This will enable to debug programs that fail along with host function calls (invalid table structures, invalid soroban functions, bad host-side conversions, etc).
The text was updated successfully, but these errors were encountered:
Even if writing zephyr programs is quite simple and writing code that's formally incorrect is difficult, when that happens debugging is currently very difficult. Not to mention that some soroban host functionalities are not yet supported and when used will inevitably result in SVM errors that are not debuggable client-side.
To improve this we should carry host-side stack traces about potential raised errors. This will enable to debug programs that fail along with host function calls (invalid table structures, invalid soroban functions, bad host-side conversions, etc).
The text was updated successfully, but these errors were encountered: