You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.
rbpf does not allow symbol names greater than 64 bytes, and in #303 I have needed to generate symbol names larger than that. rustc generates huge symbol names but they are stripped before running on solana.
It seems that we have just been lucky that move-native has not generated any huge symbol names, as that library is not stripped.
Solana does this in the cargo-build-sbf tool by using its strip.sh script. That script essentially just calls llvm-objcopy --strip-all on the .so file.
I am unsure where exactly we should do this. For now we might be able to just do it in rbpf-tests.
The text was updated successfully, but these errors were encountered:
In rbpf-tests.rs the linker command already adds an option to strip all symbols. We might have to keep move-native symbols short or replace them by hashes, assuming we can avoid collisions.
yeah i remember we ran into this issue only a while back and @dmakarov found out this issue with long symbol names. I we'll get linker error if long symbol names are present in a binary for some reason.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
rbpf does not allow symbol names greater than 64 bytes, and in #303 I have needed to generate symbol names larger than that. rustc generates huge symbol names but they are stripped before running on solana.
It seems that we have just been lucky that move-native has not generated any huge symbol names, as that library is not stripped.
Solana does this in the
cargo-build-sbf
tool by using itsstrip.sh
script. That script essentially just callsllvm-objcopy --strip-all
on the .so file.I am unsure where exactly we should do this. For now we might be able to just do it in rbpf-tests.
The text was updated successfully, but these errors were encountered: