TAPSET::CONTEXT-UNWIND(3stap)

💅 TAPSET::CONTEXT-UNWIND — the 3stap manual page, bestie edition 🎀

okay so real quick, before we even get into it: this is tapset::context-unwind, aka the systemtap context-unwind tapset ✨ and she's here to spill the tea on where your event actually happened.

---

🌸 NAME 🌸

tapset::context-unwind — the systemtap context-unwind tapset, no cap 💖

---

✨ DESCRIPTION ✨

okay so picture this: something happens in your kernel and you're like where did that even come from?? 😭 That's literally what these context functions are for — they hand you the extra deets about where an event occurred. We're talking a whole backtrace back to the scene of the crime, plus the current register values for the processor. it's giving forensic investigator 💅

---

🦋 print_backtrace

Print kernel stack back trace 🔥

See function::print_backtrace(3stap) for details.

---

🦋 print_backtrace_fileline

Print kernel stack back trace 🔥

See function::print_backtrace_fileline(3stap) for details.

---

🦋 sprint_backtrace

Return stack back trace as string ✨ (yes bestie, she returns it — you get to keep it)

See function::sprint_backtrace(3stap) for details.

---

🦋 backtrace

Hex backtrace of current kernel stack 👑

See function::backtrace(3stap) for details.

---

🦋 task_backtrace

Hex backtrace of an arbitrary task 🌈 (not just the current one, we're flexible like that)

See function::task_backtrace(3stap) for details.

---

👀 SEE ALSO 👀

• function::print_backtrace(3stap)
• function::print_backtrace_fileline(3stap)
• function::sprint_backtrace(3stap)
• function::backtrace(3stap)
• function::task_backtrace(3stap)
• stap(1)
• stapprobes(3stap)

---

🫶 that's the whole page, bestie — go forth and backtrace responsibly

mwah 💋 this came to you courtesy of the SystemTap Tapset Reference, dated September 2026, and yeah the title up top is literally TAPSET::CONTEXT-UNWIND(3stap) — iconic of her 💜