ruby: disable backtrace#15022
Merged
DavidKorczynski merged 1 commit intogoogle:masterfrom Feb 25, 2026
Merged
Conversation
Signed-off-by: Adam Korczynski <adam@adalogics.com>
DavidKorczynski
approved these changes
Feb 25, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 removes backtrace from the ruby build. The reason we want to remove that is to disable this code block. From what I can tell, this code block breaks the coverage build; When clang compiles a codebase with coverage instrumentation (-fcoverage-mapping), it can produce a malformed record in the __llvm_covfun ELF section — a ULEB128 value has its continuation bit set but no following byte. Since llvm-cov parses the section sequentially and aborts on the first malformed record, this single bad record (193 bytes out of ~7.4 MB in Rubys case during local testing) causes the entire coverage report to show 0%. This is the case with the Ruby coverage report: The coverage report builds but it incorrectly shows 0% coverage. I don't know why that code block causes that, perhaps it is the inline include.