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

Get backtraces working in compiled code, for debugging use #1110

Closed
headius opened this issue Oct 10, 2013 · 1 comment
Closed

Get backtraces working in compiled code, for debugging use #1110

headius opened this issue Oct 10, 2013 · 1 comment

Comments

@headius
Copy link
Member

headius commented Oct 10, 2013

While exploring #1086, I realized that tracing had degraded to the point of only working in the interpreter again, even though logic exists to be able to trace in compiled code. The primary reason for this is due to the fact that compiled code has never gained the ability to update our artificial backtrace.

This is not a great deal of work, but it will be a little fiddly. At minimum, the following need to happen:

  • The wrappers for compiled methods and blocks need to do c_call (and b_call for blocks). This may still be working, but it depends on backtrace being up to date.
  • Compiled wrappers must push and pop backtrace when tracing is enabled.
  • Compiled code must update line number as the line progresses.

With these in place I believe it's possible to have compiled tracing work properly.

Of course, if we just wrote our own debugger, this might be a moot point.

@headius
Copy link
Member Author

headius commented Oct 2, 2015

This is now a defunct bug. Tracing is added to all code (interpreted OR jitted) by instructions in IR. We'll call this fixed in 9k.

@headius headius closed this as completed Oct 2, 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

2 participants