Binary's probe must be in this format, and exported to match the probe symbol.

const ProbeKind = enum(u8) { init, deinit, reset_all };
noinline fn lifetime_probe(idx: u32, kind: ProbeKind) callconv(.C) void {
    std.mem.doNotOptimizeAway(idx);
    std.mem.doNotOptimizeAway(kind);
}

Usage:

RUST_LOG=info cargo run --release --config 'target."cfg(all())".runner="sudo -E"' -- --lifetime-probe-symbol=your_lifetime_probe --binary-path=/[..]/bin

1. stable rust toolchains: rustup toolchain install stable
2. nightly rust toolchains: rustup toolchain install nightly --component rust-src
3. (if cross-compiling) rustup target: rustup target add ${ARCH}-unknown-linux-musl
4. (if cross-compiling) LLVM: (e.g.) brew install llvm (on macOS)
5. (if cross-compiling) C toolchain: (e.g.) brew install filosottile/musl-cross/musl-cross (on macOS)
6. bpf-linker: cargo install bpf-linker (--no-default-features on macOS)

Use cargo build, cargo check, etc. as normal. Run your program with:

cargo run --release --config 'target."cfg(all())".runner="sudo -E"'

Cargo build scripts are used to automatically build the eBPF correctly and include it in the program.

Cross compilation should work on both Intel and Apple Silicon Macs.

CC=${ARCH}-linux-musl-gcc cargo build --package myapp --release \
  --target=${ARCH}-unknown-linux-musl \
  --config=target.${ARCH}-unknown-linux-musl.linker=\"${ARCH}-linux-musl-gcc\"

The cross-compiled program target/${ARCH}-unknown-linux-musl/release/myapp can be copied to a Linux server or VM and run there.