FUNCTION::SPRINT_BAC(3stap)

πŸ’– FUNCTION::SPRINT_BAC β€” the 3stap girlies know πŸ’–

okay so bestie, welcome to the Context Functions corner of the SystemTap Tapset Reference (yes, that's the 3stap manual, we're fancy here) ✨


🌸 NAME 🌸

function::sprint_backtrace β€” returns the stack back trace as a string, no cap 🫢


πŸŽ€ SYNOPSIS πŸŽ€

sprint_backtrace:string()

πŸ¦‹ ARGUMENTS πŸ¦‹

None. literally nothing, she takes no arguments, she's low maintenance πŸ’…


✨ DESCRIPTION ✨

okay so here's the tea β˜• β€” sprint_backtrace returns a simple (kernel) backtrace. and the format?? one line per address, periodt. each of those lines includes:

  • the symbol name β€” or, if the symbol couldn't be resolved, the hex address instead πŸ™ˆ
  • the module name, if one was found

and it also includes the offset from the start of the function if that's found. but if it isn't found, the offset gets added to the module instead (if found, and it shows up between brackets) πŸŽ€

she hands the whole backtrace back to you as a string, and every single line is terminated by a newline character. slay.

⚠️ heads up bestie, this is the important part: the returned stack gets truncated to MAXSTRINGLEN. so if you want fuller and richer stacks, you gotta use print_backtrace instead. don't come crying to me when your stack gets cut off πŸ’€

she's also equivalent to sprint_stack(backtrace) β€” but she's more efficient πŸ‘‘ because there's no need to translate between hex strings and the final backtrace string. she just gets it. main character energy fr fr πŸ”₯


🌈 SEE ALSO 🌈


SystemTap Tapset Reference Ver 🌸 September 2026 β€” mwah, that's the version and the date, love u, bye bestie πŸ’–βœ¨πŸ¦‹πŸŽ€

πŸ“¦ where this page comes from