[GR-68567] Improve GDB backtrace support for lazy deoptimizations. #11972
+62
−64
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…che and update handling of lazy deopt frames. Update runtimedebuginfotests. Combine release and releaseOnTeardown for code observers.
oracle-contributor-agreement
bot
added
the
OCA Verified
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For lazy deoptimizations we still can continue to use the .debug_frame information of the run-time debug info for an optimized method in the backtrace in GDB.
We just need to make sure that debug info will only get cleaned up when the
CodeInfoof the corresponding run-time compilation is really removed from theRuntimeCodeCache.In the gdb-debughelpers we just need to make sure to properly unwind and print the frame for a
lazyDeoptStub.