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

Kernel Invocation Error Reporting #27

Open
gilbo opened this issue May 31, 2014 · 0 comments
Open

Kernel Invocation Error Reporting #27

gilbo opened this issue May 31, 2014 · 0 comments

Comments

@gilbo
Copy link
Owner

gilbo commented May 31, 2014

Right now, any error that happens while a kernel is running will cause a stack dump to report the error as originating within our compiler. That's bad for us.

There are two stages to fixing this:

  1. Wrap all kernel invocations in a Lua xpcall() that produces a slightly more useful stack dump. That is, the stack dump should locate the error at the kernel call site instead.
  2. Eventually, we'd like to plumb line-number information from the parser through to the Terra code-gen and then somehow have terra dump more useful debug information. This may be difficult and requires Zach's input.
@gilbo gilbo added this to the Legion single-core perf and Features milestone Jun 3, 2015
@gilbo gilbo self-assigned this Jun 3, 2015
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

1 participant