FUNCTION::THREAD_INDENT_DEPTH(3stap)

✨ FUNCTION::THREAD_INDENT_DEPTH(3stap) ✨

okay so bestie, we're in the SystemTap Tapset Reference β€” the Utility functions for using an... part of the manual, the 3stap section, and this is the page for function::thread_indent_depth. πŸ’…


πŸŽ€ NAME πŸŽ€

function::thread_indent_depth β€” returns the nested-depth of the current task 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

thread_indent_depth:long(delta:long)

like, that's the whole signature, no notes. πŸ‘‘


πŸ“ ARGUMENTS πŸ“

  • delta β€” the amount of depth added/removed for each call. so it's giving "how much do we move the depth needle by" every single time you call her. πŸ’–

🌈 DESCRIPTION 🌈

bestie listen. This function returns an integer equal to the nested function-call depth starting from the outermost initial level. That's it, that's the whole job. 🫢

And why do we care? Because this function is useful for saving space (specifically the space consumed by all that whitespace) in traces that have long, deeply nested function calls. Basically it's the anti-whitespace queen, keeping your trace cute and compact instead of letting it spread out like an unformatted group chat. ✨

Use this function in a similar fashion to thread_indent, okay? iykyk. Like literally:

  • in a call-probe, use thread_indent_depth(1)
  • in a return-probe, use thread_indent_depth(-1)

up and down, in and out, main character energy, the depth just tracks. πŸŽ€


πŸ’œ SEE ALSO πŸ’œ


fr fr, don't forget the -1 on the return-probe. you go in with 1, you come out with -1, that's the vibe check. πŸ’€

and that's a wrap babes! πŸ’– This lil love letter came to you from the SystemTap Tapset Reference, version Ver (yes that's literally what the footer says, don't @ me), dated September 2026. slay, read responsibly, and go indent some traces. πŸŒΈπŸ¦‹πŸŽ€

πŸ“¦ where this page comes from