Skip to content

chore(deps): bump blazesym to 0.2.3 for build-id debug file lookup#1637

Closed
xroche wants to merge 1 commit intoDataDog:mainfrom
xroche:bump/blazesym-0.2.3
Closed

chore(deps): bump blazesym to 0.2.3 for build-id debug file lookup#1637
xroche wants to merge 1 commit intoDataDog:mainfrom
xroche:bump/blazesym-0.2.3

Conversation

@xroche
Copy link
Copy Markdown
Contributor

@xroche xroche commented Feb 28, 2026

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
-dbgsym packages. These packages store debug files at build-id paths
(/usr/lib/debug/.build-id/XX/rest.debug), but blazesym only searches GNU
debuglink 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=true has no effect on
stripped 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.3
  • symbolizer-ffi/Cargo.toml: blazesym-c 0.1.0-rc.2=0.1.7
  • Cargo.lock updated accordingly

No code changes needed — the breaking API change (code_info became
Option<Box<CodeInfo>>) is transparent through Rust's auto-deref.

References

Test plan

  • cargo build --workspace passes
  • cargo clippy --workspace --all-targets --all-features -- -D warnings passes
  • CI pipeline passes

🤖 Generated with Claude Code

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]>
@xroche xroche force-pushed the bump/blazesym-0.2.3 branch from 14c9df8 to e71c2ce Compare February 28, 2026 10:35
@xroche xroche marked this pull request as ready for review February 28, 2026 10:36
@xroche xroche requested review from a team as code owners February 28, 2026 10:36
@r1viollet r1viollet added profiling Relates to the profiling* modules. crashtracker AI Generated PR largely written by AI tools labels Mar 4, 2026
@r1viollet
Copy link
Copy Markdown
Contributor

running CI might be failing against remote repositories

Run set -uo pipefail
Fetching base branch: main
Using base ref: origin/main
Warning: Failed to diff against origin/main, exiting

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.24%. Comparing base (d4c7824) to head (e71c2ce).
⚠️ Report is 3 commits behind head on main.

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     
Components Coverage Δ
libdd-crashtracker 63.13% <ø> (+0.11%) ⬆️
libdd-crashtracker-ffi 16.71% <ø> (+0.61%) ⬆️
libdd-alloc 98.77% <ø> (ø)
libdd-data-pipeline 87.87% <ø> (+0.04%) ⬆️
libdd-data-pipeline-ffi 74.15% <ø> (-0.49%) ⬇️
libdd-common 79.73% <ø> (ø)
libdd-common-ffi 73.40% <ø> (ø)
libdd-telemetry 62.48% <ø> (ø)
libdd-telemetry-ffi 16.75% <ø> (ø)
libdd-dogstatsd-client 82.64% <ø> (ø)
datadog-ipc 80.86% <ø> (+0.11%) ⬆️
libdd-profiling 81.59% <ø> (-0.02%) ⬇️
libdd-profiling-ffi 63.65% <ø> (ø)
datadog-sidecar 33.96% <ø> (+1.70%) ⬆️
datdog-sidecar-ffi 14.63% <ø> (+7.43%) ⬆️
spawn-worker 54.69% <ø> (ø)
libdd-tinybytes 93.16% <ø> (ø)
libdd-trace-normalization 81.71% <ø> (ø)
libdd-trace-obfuscation 94.67% <ø> (ø)
libdd-trace-protobuf 68.00% <ø> (ø)
libdd-trace-utils 88.97% <ø> (-0.21%) ⬇️
datadog-tracer-flare 86.86% <ø> (-2.10%) ⬇️
libdd-log 74.69% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@r1viollet
Copy link
Copy Markdown
Contributor

opening a new PR here to fix some of the linter issues

@r1viollet r1viollet closed this Mar 4, 2026
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI Generated PR largely written by AI tools crashtracker profiling Relates to the profiling* modules.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants