Coverage tooling today assumes you control the build. You add flags, compile twice, maintain separate instrumented artifacts. At scale, with hundreds of thousands of packages, multiple languages, this compounds into real operational burden.

xcover takes a different approach: eBPF uprobes attach to any compiled binary at runtime, no source changes, no build flags, no instrumentation. The binary you ship to production is the binary you test. One tool, any language, any binary.

This talk walks through how xcover works, how it handles stripped binaries via function recovery, and what the real overhead numbers look like, because the data matters.

We'll also look at what's next for xcover: removing the kernel trap cost with userspace BPF runtimes. Active experiment, hypothesis worth exploring out loud