Mask native elements for MRI backtrace #9155
Draft
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds off of #9154 by also masking internal frames for MRI-formatted backtrace elements. It appears at some point we started showing Java lines in the MRI-formatted trace:
This differs from user expectations and the contents of
callertraces, which both filter out internal methods (native or Ruby) by replacing them with the most recent external Ruby frame (CRuby also implementsInteger#/in native code):The patch here simply uses the
callerbacktrace-gathering logic for the MRI-mode backtrace data.This is opened as a draft because I'm unsure how long this behavior has been broken, and I'm not sure what impact fixing it will have yet. Being based on #9154, that PR should be merged first, but this one needs more evaluation.