FUNCTION::USYMDATA(3stap)

πŸ’– FUNCTION::USYMDATA πŸ’–

okay bestie, welcome to function::usymdata from the 3stap manual β€” yes that's the SystemTap tapset section, we're doing real systems work today and we're doing it cutely ✨


🌸 NAME 🌸

function::usymdata β€” return the symbol and module offset of an address. that's it, that's the whole job, and she does it flawlessly πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

usymdata:string(addr:long)

look at her. one arg, returns a string. iconic behavior πŸŽ€


πŸ“ ARGUMENTS πŸ“

  • addr β€” the address you want translated. that's the one and only thing you're handing over, no cap 🫢

✨ DESCRIPTION ✨

so here's the tea, bestie β˜• β€” this function returns the (function) symbol name associated with the given address in the current task, if it's known. and it doesn't stop there: you also get the offset from the start and the size of the symbol, plus the module name (and yes, the module name comes between brackets) πŸ’–

but wait, there's more, because sometimes life is messy 😭 β€” if the symbol is unknown but the module is known, then instead you get the offset inside the module, plus the size of the module. slay, we adapt.

and the rule for missing pieces? if any element is not known, it just gets omitted β€” no drama, no placeholder, she simply leaves it out πŸ™ˆ

aaaand finally: if the symbol name is unknown, she'll return the hex string for the given address. so you always get something back. main character energy fr fr πŸ‘‘


🌈 SEE ALSO 🌈


that's the whole page bestie, every flag, every value, every vibe, nothing skipped πŸ’œ

okay bye my love β€” this was the SystemTap Tapset Reference, dated September 2026 (the footer's version field just says Ver, keeping it mysterious πŸ’€), and you absolutely ate this documentation. periodt. πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from