FUNCTION::PRINT_UBAC(3stap)

✨ FUNCTION::PRINT_UBAC(3stap) ✨

okay bestie, welcome to the Context Functions corner of the SystemTap Tapset Reference (section 3stap, we're fancy like that πŸ’…). pull up a chair, we're talking stack backtraces πŸ¦‹


πŸŽ€ NAME πŸŽ€

function::print_ubacktrace β€” prints the stack back trace for the current user-space task. yes, the current user-space task. she's nosy like that πŸ’–


🌸 SYNOPSIS 🌸

1) print_ubacktrace()

2) print_ubacktrace(pc:long,sp:long,fp:long)

πŸ’œ ARGUMENTS πŸ’œ

  • pc β€” override PC 🫢
  • sp β€” override SP 🫢
  • fp β€” override FP 🫢

like, you get to hand-pick the registers instead of letting her figure it out herself. main character behaviour fr.


✨ DESCRIPTION ✨

  1. the plain one β€” no extra deets, she just does the thing.
  2. this one is equivalent to print_ustack(ubacktrace), EXCEPT that deeper stack nesting may be supported. Returns nothing (ngl, she's a yapper not a gifter β€” no return value, periodt). Wanna see the kernel version instead? See print_backtrace for kernel backtrace πŸ‘‘

she's also equivalent to print_ubacktrace, but she does the backtrace using the pc, sp, and fp that you provide. Useful.


πŸ’€ NOTE πŸ’€

bestie, listen. if you want (full) backtraces for user space applications and shared libraries that aren't mentioned in the current script, you have to run stap with -d /path/to/exe-or-so and/or add --ldd to load all the needed unwind data. no shortcut, no cap. that's the whole vibe check right there 😭

(also the original page says "shared shared libraries" and honestly? iconic. we stan a typo πŸ‘‘)


🌈 SEE ALSO 🌈

(yes, it's listed twice. twinning fr fr 🫢)


SystemTap Tapset Reference, version whatever-the-hell-it-says, dated September 2026 β€” and that's the whole page, bestie! go forth and unwind those stacks πŸŒΈβœ¨πŸ’– πŸ¦‹ πŸŽ€

πŸ“¦ where this page comes from