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

Print stack trace instead of just source code line #808

Open
ingomueller-net opened this issue Nov 17, 2020 · 0 comments
Open

Print stack trace instead of just source code line #808

ingomueller-net opened this issue Nov 17, 2020 · 0 comments

Comments

@ingomueller-net
Copy link
Contributor

With functions and modules that may be (transitively) called from several places in the query, it would be very useful to provide a stack trace instead of just the source code location of the top stack frame. Otherwise, the different possible calls to the location where the error occurs are indistinguishable.

A more involved solution might also provide variable bindings, maybe even for all stack frames.

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

No branches or pull requests

2 participants