CKB Pulse

All lessons · Developer tooling · Start here · Glossary

Profile spawned scripts with the right ELF symbolsWorkingFrom one fix

From one fix · Check: right · Checked 2026-11-19

In ckb-debugger full mode with spawn, coverage, flamegraph and overlap analysis now use the ELF of the VM chosen with --vm-id instead of the root program. Pass an unstripped binary with --vm-symbols to get symbols and debug info.

Why it matters: Before this change, full-mode coverage, flamegraph and overlap reports for a spawned child VM were built from the root program's ELF. The child's addresses were resolved against the wrong symbols, so the profile of that script was misleading.

Older ckb-debugger versions profile spawned children with the root program's symbols, so their profiles are wrong.

Pattern

MachineFlamegraph::new(&verifier_program_elf) -> MachineFlamegraph::new(&machine_program_elf or --vm-symbols file)

A test changed in the same commit

It sits next to the fix. We did not run it.

Concepts
Testing and devnet
Evidence
From one fix: from one project, checked against its commit
First seen
2026-11-16
Last changed
2026-11-16
Last checked
2026-11-19
Check against the commit
right: the lesson follows from its commit and still holds in the code today

Sources (1)

More about Developer tooling

All 35 in this topic

Do you maintain a project this lesson came from? Confirm or correct it

Cite this lesson
LusoCryptoLabs, "Profile spawned scripts with the right ELF symbols", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/profile-spawned-scripts-with-the-right-elf-symbols, CC BY 4.0, last changed 2026-11-16.

Drawn from public commits and checked against the commit each one came from and the project's code today. Read the source before you rely on one. Text under CC BY 4.0: credit LusoCryptoLabs, CKB lessons, with a link to the lesson. Want a lesson changed or removed? Open an issue.