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.

Sign up for GitHub

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

Jump to bottom

Call trace for better debugging experience #618

Open

raviqqe opened this issue Jan 4, 2022 · 0 comments

Labels

Contributor

raviqqe commented Jan 4, 2022 •

edited

Problem

The language doesn't support something like call stack dump on errors.
Because we use CPS (continuation passing style) internally, we need to implement a custom solution to track function calls by ourselves.

Solution

Track function calls in CPS stacks.
Dump them as logs or let higher-level IR capture the call traces on errors.
- However, this can be just huge noise for large programs.

raviqqe added the enhancement label

raviqqe changed the title ~~Call stack/trace for better debugging experience~~ Call trace for better debugging experience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment