-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Upload libc.so.6 and ld-linux-x86-64.so.2 in PostBuild symbol uploads when cross compiling #73950
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️ |
@Swatinem @loewenheim mind taking a look at this? |
Hm, are those files we would expect the user to upload? Or should they be on a public symbol server @Swatinem ? |
The only Linux distribution which we have a builtin symbol server for is Ubuntu at the moment. And we have already seen that Ubuntu happily removes outdated debug files from their server. So even in that case, its quite possible that no debug symbols can be found. I would recommend to either figure out if the distribution offers a stable symbol server and configure that, or to just upload those debug files manually. See sentry/src/sentry/conf/server.py Lines 2763 to 2786 in 56f7906
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Problem Statement
You get this error when emitting events from a linux server
It's a bit unclear how best to go about uploading these debug files, particularly when cross compiling
Solution Brainstorm
I tried uploading all the debug symbols available from the linux toolchain, however this didn't solve my issue as neither of the libc.so.6 files uploaded matched the debug id
Product Area
Unknown
The text was updated successfully, but these errors were encountered: