Valgrind Callgrind

Inspect instrumented instruction costs for a real workload. A plan checks availability and describes a command; it does not execute it.

From examples/kitchen-sink in the source checkout, run julia setup-linux.jl on Linux or WSL. Start Julia with julia --project=.controller/linux to plan the supplied native-workload.jl:

using PerfChecker
plan = native_tool_plan(:callgrind, "native-workload.jl";
    project=dirname(Base.active_project()), output="exports/callgrind")
display(plan["availability"])
display(plan["arguments"])

From the same directory, prepare the native support files and run only this tool:

julia --startup-file=no --project=.controller/linux setup-native.jl
julia --startup-file=no --project=.controller/linux native-run.jl datastructures callgrind

The existing Linux/Julia 1.13.0 receipt uses 512 events and three lifecycles, including startup. Recorded status: completed, exit 0, callgrind.1663 and log. The workload oracle passed.

Instruction counts are instrumented work, not native elapsed time.

The separate windowed receipt records 550,591 instrumented instructions, excluding startup but including preparation and the oracle for three warmed lifecycles. These boundaries differ from the ordinary capture above.

Oxygen has separate per-tool receipts; inspect its completion/timeout states instead of transferring a container-workload verdict.