-
Notifications
You must be signed in to change notification settings - Fork 77
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
Splitting Debuginfo #30
Comments
We generate the pdb and upload it to the release, however we don't:
|
dwp is blocked on rust-lang/cargo#11572 dsyms would be nice to do before shipping... |
The cargo issue was fixed (obvs needs to ride the trains) but rust-lang/rust#105991 is also an argument against using it. |
Some additional info for macOS symbol servers: The alternatives are described here: https://lldb.llvm.org/use/symbols.html As for a macOS symbol server URL scheme, for the Mozilla symbol server I'm planning to use the following scheme: https://symbols.mozilla.org/uuid/D13BD7EC88D830C49C6BC4B34F2D9156/debuginfo.dSYM.tar.bz2 And then we can supply an off-the-shelf script for use with |
There is some work planned to cleanup the mess of symbol formats in rustc so it's easier to just ask for the right thing. Notably a new post-link debuginfo on linux would produce the more traditional and imo superior "strip" debuginfo format, which has the same basic properties as pdb and dSYM. With this you should be able to uniformly ask for a fully stripped binary and a completely independent native symbol file that contains all the info "missing" from the binary. All standard tools would know how to handle these, and you'd be able to do either online or offline debugging of binary/crash (with the appropriate machinery to fetch the symbols from servers). It's possible this format can be manually "polyfilled" by cargo-dist since it is apparently a case of just using the |
feat: WorkspaceInfo inherits new PackageInfo features
Another future killer app: properly setting the flags and running the tools to produce proper symbol/debuginfo files (similar to source maps, but for native code).
This comment covers a lot of useful details on the state of this stuff in rust.
Some quick notes:
Each platform has different formats for this:
Different platforms have different symbol servers:
To generate symbol files for rust you want to:
Then the user will want to:
The text was updated successfully, but these errors were encountered: