CKB Pulse

全部经验 · Developer tooling · 从这里开始 · 术语表

Mock syscalls must write back output length进阶来自一次修复

来自一次修复 · 核对结果:正确 · 核对于 2026-11-19

When a ckb-vm mock or fuzzing syscall layer implements inherited_fds, it must store the fd count back into length_addr with store64 after writing the fd buffer. Otherwise the script reads back the capacity it passed in and treats unwritten slots as fds. ckb-vm-contrib's fuzzing utils lacked this until v1.1.2.

为什么重要: Without the write back, a script running under the mock sees the capacity it passed in as the fd count and diverges from real CKB behaviour.

代码模式

syscall handler writes data to the buffer but never calls machine.memory_mut().store64(&length_addr, wrote_length)
概念
Testing and devnet
证据
来自一次修复: 来自一个项目,已对照其提交核对
首次出现
2026-11-16
最近改动
2026-11-16
最近核对
2026-11-19
对照提交的核对结果
正确:这条经验出自该提交,并且在今天的代码中仍然成立

来源(1)

更多关于Developer tooling

查看此主题的全部 35 条

你维护这条经验的来源项目吗?请确认或纠正

引用这条经验
LusoCryptoLabs, "Mock syscalls must write back output length", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/mock-syscalls-must-write-back-output-length, CC BY 4.0, last changed 2026-11-16.

取自公开提交,并对照每条经验的来源提交和项目当前代码做了核对。使用前请先读来源。 文本采用 CC BY 4.0:请署名 LusoCryptoLabs, CKB lessons,并附上经验的链接。 想修改或撤下某条经验?请提交 issue。