FUNCTION::PROBE_TYPE(3stap)

💖 NAME 💖

function::probe_type — the low level probe handler type of the current probe, bestie. that's it, that's the whole vibe ✨

---

🦋 SYNOPSIS 🦋

probe_type:string()

---

🎀 ARGUMENTS 🎀

None. nothing. zero. no arguments, no drama, she takes no input 💅

---

🌸 DESCRIPTION 🌸

okay so probe_type hands you back a short string that describes the low level probe handler type for whatever probe point you're currently chillin' in. that's the whole job. slay.

heads up tho — this is for informational purposes only. she's not here to do heavy lifting, she's here to tell you what kind of handler you're dealing with. periodt.

here's the tea: depending on which low level probe handler you've got, different context functions can or cannot give you info about the current event. like, for example — some probe handlers only trigger in user space and have no associated kernel context at all. so if you're reaching for kernel context there, that's a no. 🙈

and one more thing, high-level probes might map to the same or different low-level probes — it just depends on the systemtap version and/or the kernel you're running. iykyk. it's giving "it depends" energy but that's literally just how it is. 🔥

---

⭐ SEE ALSO ⭐

• tapset::context(3stap)

---

SystemTap Tapset Reference, version September 2026 🫶 this was your girl FUNCTION::PROBE_TYPE from the 3stap manual, signing off — stay curious, stay iconic, and go read tapset::context(3stap) next, ok bye bestie 💖✨🎀🦋🌸