Skip to content

Rust debug information symbolicator not working #88294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
lfdominguez opened this issue Mar 17, 2025 · 10 comments
Closed
1 task done

Rust debug information symbolicator not working #88294

lfdominguez opened this issue Mar 17, 2025 · 10 comments

Comments

@lfdominguez
Copy link

Self-Hosted Version

25.2.0

CPU Architecture

x86_64

Docker Version

28.0.1

Docker Compose Version

2.33.1

Machine Specification

  • My system meets the minimum system requirements of Sentry

Steps to Reproduce

  1. Compile release with debug info my rust app
  2. Use sentry-cli with the upload-dif command to upload debug information
  3. Start app and send a crash report

Expected Result

See debug symbolization information on issue page

Actual Result

  • Issue View: All errors (warning sign) are "This frame has an unknown problem and can not be symbolicated"

Image

  • Debug Info already sent:

Image

Event ID

No response

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Mar 17, 2025
@lfdominguez lfdominguez changed the title Rust debug information symbolication not working Rust debug information symbolicator not working Mar 17, 2025
@aldy505
Copy link
Contributor

aldy505 commented Mar 29, 2025

@dalnoki @InterstellarStella Hello! Can you help transferring this to sentry and assign the Product Area: Processing for triage? Us at self-hosted does not have any idea about this issue. Thanks!

@InterstellarStella InterstellarStella transferred this issue from getsentry/self-hosted Mar 31, 2025
@getsantry
Copy link
Contributor

getsantry bot commented Mar 31, 2025

Routing to @getsentry/product-owners-processing for triage ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Mar 31, 2025

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Mar 31, 2025

Routing to @getsentry/product-owners-processing for triage ⏲️

@tobias-wilfert
Copy link
Member

tobias-wilfert commented Apr 1, 2025

Can you provide us with the event payload (if you don't want to post it in public please send to tobias.wilfert@sentry.io).

@lfdominguez
Copy link
Author

lfdominguez commented Apr 9, 2025

Can you provide us with the event payload (if you don't want to post it in public please send to tobias.wilfert@sentry.io).

Payload sent

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Apr 9, 2025
@loewenheim
Copy link
Contributor

Hi! There seem to be two problem with your event:

  1. Most frames (all the ones that have the "unknown problem") aren't covered by any debug image in the event. They have addresses like 0x5a0xxxxxxxxx but all the images sent with the event have addresses like 0x73dxxxxxxxxx. This means that even if you've uploaded the debug files to your project, we can't find them because your event doesn't mention them. It seems that all debug files included in your event are system files (libpthread and such), that is certainly suspicious.
  2. Two frames are referring to glibc, which is included in your event, but the debug files can't be found. Whether that is because you haven't uploaded them or for another reason I can't say.

Your first priority should be to find out why the needed images aren't included in the event payload. The right repo for this would be sentry-rust.

@lfdominguez
Copy link
Author

Checking my event.json file I see the same, all the debug meta images referred are native libraries and the application binary itself is missing, this is the error right? Thanks, I will open an issue on sentry-rust

@lfdominguez
Copy link
Author

Closing because moved to getsentry/sentry-rust#767
Thanks guys for the support

@loewenheim
Copy link
Contributor

Please reach out if we can help you further!

@github-actions github-actions bot locked and limited conversation to collaborators Apr 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Archived in project
Development

No branches or pull requests

5 participants