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
If you build an archive with LLVM that is over 4GB, it writes a /SYM64/ table entry instead of / (see writeSymbolTableHeader). This prevents ArchiveFile from being able to load the names and symbols here. One way this fails is when iterating over the members of the archive, and an archive member's name is too long, it will fail here because the names data is empty.
The text was updated successfully, but these errors were encountered:
Let me know how you want this released. I'm not sure if you need this in a patch release of some older object version, or a new release (there's currently unreleased breaking changes), which would mean updating the rest of the ecosystem too (e.g. addr2line and backtrace).
Fix loading large rlibs
Bumps object crate to permit parsing archives with 64-bit table entries. These
are primarily encountered when there's more than 4GB of archive data.
cc gimli-rs/object#365
Helps with rust-lang#88351, but will also need a beta backport
r? `@ehuss` (mostly for the test)
If you build an archive with LLVM that is over 4GB, it writes a
/SYM64/
table entry instead of/
(seewriteSymbolTableHeader
). This preventsArchiveFile
from being able to load the names and symbols here. One way this fails is when iterating over the members of the archive, and an archive member's name is too long, it will fail here because thenames
data is empty.The text was updated successfully, but these errors were encountered: