chore(deps): bump blazesym to 0.2.3 for build-id debug file lookup#1637
Closed
xroche wants to merge 1 commit intoDataDog:mainfrom
Closed
chore(deps): bump blazesym to 0.2.3 for build-id debug file lookup#1637xroche wants to merge 1 commit intoDataDog:mainfrom
xroche wants to merge 1 commit intoDataDog:mainfrom
Conversation
blazesym 0.2.3 adds build-id debug file lookup, fixing symbolization of stripped binaries with split debug info from Debian/Ubuntu -dbgsym packages. Co-Authored-By: Claude Opus 4.6 <[email protected]>
14c9df8 to
e71c2ce
Compare
Contributor
|
running CI might be failing against remote repositories |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1637 +/- ##
==========================================
+ Coverage 71.08% 71.24% +0.15%
==========================================
Files 424 424
Lines 62493 62514 +21
==========================================
+ Hits 44426 44535 +109
+ Misses 18067 17979 -88
🚀 New features to boost your workflow:
|
Contributor
|
opening a new PR here to fix some of the linter issues |
gh-worker-dd-mergequeue-cf854d bot
pushed a commit
that referenced
this pull request
Mar 5, 2026
# What does this PR do? blazesym 0.2.3 adds build-id debug file lookup, fixing symbolization of stripped binaries with split debug info from Debian/Ubuntu -dbgsym packages. # Motivation Better symbolication for crashtracking and `ddprof` # Additional Notes Changed proposed by @xroche [here](#1637) # How to test the change? No change in features in this PR. Co-authored-by: xroche <[email protected]> Co-authored-by: erwan.viollet <[email protected]>
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
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.
Summary
Bump blazesym from 0.2.0-rc.5 to 0.2.3 (and blazesym-c from 0.1.0-rc.2 to 0.1.7).
Motivation
blazesym 0.2.0-rc.5 cannot find split debug files installed by Debian/Ubuntu
-dbgsympackages. These packages store debug files at build-id paths(
/usr/lib/debug/.build-id/XX/rest.debug), but blazesym only searches GNUdebuglink paths (
/usr/lib/debug/usr/bin/<name>).blazesym v0.2.3 added build-id debug file lookup
(libbpf/blazesym#1415),
fixing this for all consumers including ddprof.
Without this fix,
DD_PROFILING_INLINED_FUNCTIONS=truehas no effect onstripped binaries with split debug info — flame graphs show binary names
instead of function names.
See also: DataDog/ddprof#502
Changes
libdd-crashtracker/Cargo.toml: blazesym=0.2.0-rc.5→=0.2.3symbolizer-ffi/Cargo.toml: blazesym-c0.1.0-rc.2→=0.1.7Cargo.lockupdated accordinglyNo code changes needed — the breaking API change (
code_infobecameOption<Box<CodeInfo>>) is transparent through Rust's auto-deref.References
Test plan
cargo build --workspacepassescargo clippy --workspace --all-targets --all-features -- -D warningspasses🤖 Generated with Claude Code