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

Add errors trace #11

Open
heytdep opened this issue Jul 7, 2024 · 0 comments
Open

Add errors trace #11

heytdep opened this issue Jul 7, 2024 · 0 comments

Comments

@heytdep
Copy link
Member

heytdep commented Jul 7, 2024

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).

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