Skip to content
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

Open
narthur157 opened this issue Jul 8, 2024 · 6 comments

Comments

@narthur157
Copy link

Problem Statement

image
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

@getsantry
Copy link
Contributor

getsantry bot commented Jul 8, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Jul 8, 2024

Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️

@getsantry getsantry bot moved this from Waiting for: Support to Waiting for: Product Owner in GitHub Issues with 👀 3 Jul 8, 2024
@lforst
Copy link
Member

lforst commented Jul 10, 2024

@Swatinem @loewenheim mind taking a look at this?

@loewenheim
Copy link
Contributor

Hm, are those files we would expect the user to upload? Or should they be on a public symbol server @Swatinem ?

@Swatinem
Copy link
Member

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.
As more and more distributions have decided to move towards enabling frame pointers by default by now, it might not even be necessary to have unwind info in those cases, and the stack trace is "correct" even though it might not be particularly readable.

See

# === Various Linux distributions ===
# The `https://debuginfod.elfutils.org/` symbol server is set up to federate
# to a bunch of distro-specific servers, and they explicitly state that:
# > If your distro offers a server, you may prefer to link to that one directly
# In the future, we could add the following servers as well after validating:
# - https://debuginfod.opensuse.org/
# - https://debuginfod.debian.net/
# - https://debuginfod.fedoraproject.org/
# - https://debuginfod.archlinux.org/
# - https://debuginfod.centos.org/
# A couple more servers for less widespread distros are also listed, and there
# might be even more that are not listed on that page.
# NOTE: The `debuginfod` layout in symbolicator requires the `/buildid/` prefix
# to be part of the `url`.
"ubuntu": {
"type": "http",
"id": "sentry:ubuntu",
"name": "Ubuntu",
"layout": {"type": "debuginfod"},
"url": "https://debuginfod.ubuntu.com/buildid/",
"filters": {"filetypes": ["elf_code", "elf_debug"]},
"is_public": True,
},
}
for some other example symbol servers.

@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 3 Nov 1, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Nov 23, 2024

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 Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added the Stale label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Community
Development

No branches or pull requests

6 participants