The 7 Bytes That Weren't in the IDL: How #[repr(C)] Padding Breaks a Borsh Client
A single u64 added seven bytes of padding the compiler knew about and the client didn't. Here is why, and how to predict it for any #[repr(C)] struct. The failure I added one field to an instruction-a
#rust#solana#pinocchio#borsh#zero-copy#repr-c#memory-layout#struct-padding#alignment#idl#on-chain-programs#systems-programming
Responses
Markdown supported · ⌘↵ to post
No responses yet.