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

Improvements to backtrace #5851

merged 1 commit into from Aug 28, 2019

Improvements to backtrace #5851

merged 1 commit into from Aug 28, 2019


Copy link

@headius headius commented Aug 28, 2019

This PR includes improvements to how we manage the Ruby backtrace. It will fix #5849 among others.

Copy link
Member Author

@headius headius commented Aug 28, 2019

The first commit removes backtrace and frame push/pop around loads of Ruby code. Ruby code in all execution modes pushes its own frame and backtrace, so this is unnecessary and messes up backtraces.

The backtrace pushes here are not needed, since the interpreter
pushes its own backtrace (in INTERPRET_ROOT) and AOT code uses
the Java stacktrace.

The frame pushes are moved into the interpreter, since the JIT
does not need them.
@headius headius added this to the JRuby milestone Aug 28, 2019
@headius headius merged commit a4a79cf into jruby:master Aug 28, 2019
5 checks passed
@headius headius deleted the backtrace_fixes branch Aug 28, 2019
headius added a commit that referenced this issue Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

1 participant