-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
official nextest binaries could include symbols #1345
Comments
Looks like the issue was that the builder I'm using runs With the binary obtained by:
I ran
Going to get cargo-nextest 0.9.68 with this fix out in the next few days -- let's figure out the rest in the omicron issue. |
upload-rust-binary-action now aligned default strip behavior to Cargo 1.77+'s default (strip=debuginfo) (taiki-e/upload-rust-binary-action#66), so I think this workaround is no longer necessary. |
Awesome, thanks as always @taiki-e! |
As mentioned in #1345 (comment), this workaround is no longer required with the latest version of rust-upload-binary-action.
I was debugging a stuck CI worker recently, and while looking at the cargo-nextest process (which was indeed not at fault!) I discovered that there were no symbols for Rust program text in the binary:
The binary appears to have been stripped not just of debuginfo but also of all symbols:
We download this binary using:
It would be awesome if we could at least leave enough symbols in there so that debuggers can get stack traces, even if we don't end up with the full DWARF. Thanks!
The text was updated successfully, but these errors were encountered: