FUNCTION::VM_FAULT_C(3stap)

💖 FUNCTION::vm_fault_contains 💖

okay bestie, welcome to the Memory Tapset corner of the 3stap manual, and no you're not lost, this is exactly where you're supposed to be 🫶

---

✨ NAME ✨

function::vm_fault_contains — the lil guy that tests a return value so you can find out why a page fault happened 🔥

---

🦋 SYNOPSIS 🦋

vm_fault_contains:long(value:long,test:long)

that's it, that's the whole vibe. two longs walk in, one long walks out 💅

---

🎀 ARGUMENTS 🎀

• value — this is the fault_type that came back from vm.page_fault.return. like, the receipt from the fault. hand it over 🧾
• test — the kind of fault you're checking for. VM_FAULT_OOM is the classic example, or anything similar. you're basically asking "is this the reason, bestie?" 👑

---

🌸 SEE ALSO 🌸

• tapset::memory(3stap) — go read the whole memory tapset, it's giving main character energy, iykyk 📚✨

---

lowkey important: the descriptions here only tell you what the argument is, not some secret extra behaviour. so don't go inventing lore, just pass the fault type and the fault you're testing for and let the function cook 💀

---

and that's the whole page!! 🌈 this one came from the SystemTap Tapset Reference, version vibes dated September 2026, so if you're reading this from the future, hi, ily, you're doing great 💜🎀🦋

slay, you read the whole manpage, periodt ✨👑