FUNCTION::PROC_MEM_T(3stap)

💖 FUNCTION::PROC_MEM_T(3stap) 💖

okay bestie, so this one lives in the Memory Tapset of the SystemTap Tapset Reference and it's literally about how much code your process is carrying around. no cap. 🧚

---

✨ NAME ✨

function::proc_mem_txt — Program text (code) size in pages 🎀

like, the text segment. the actual instructions. the brain cells. 🧠

---

🌸 SYNOPSIS 🌸

1) proc_mem_txt:long()

2) proc_mem_txt:long(pid:long)

two whole flavors, bestie. pick your fighter. 💅

---

🦋 ARGUMENTS 🦋

• pid — The pid of process to examine 👀

that's it. that's the whole argument list. one (1) number and she's done.

---

💜 DESCRIPTION 💜

So there are two versions and they are not the same vibe, okay, let's go:

1. proc_mem_txt:long() — Returns the current process text (code) size in pages, or zero when there is no current process or the number of pages couldn't be retrieved. 🫶
2. proc_mem_txt:long(pid:long) — Returns the given process text (code) size in pages, or zero when the process doesn't exist or the number of pages couldn't be retrieved. ✨

lowkey important: both of them hand you a zero when things go sideways. zero current process? zero. process not there? zero. pages just not retrievable? you guessed it, zero. so don't be out here reading a 0 as "this process has no code," because it might be saying "girl, i couldn't get the number." 😭

the "in pages" thing is doing a lot of work here — it's pages, not bytes, not kilobytes, not a vibe. pages. periodt. 📄

---

🔥 SEE ALSO 🔥

• tapset::proc_mem(3stap) — go read the whole fam, she has siblings 👑

---

and that's the whole page, bestie!! 🌈⭐💖

this gorgeous little number comes to you from the SystemTap Tapset Reference, version dated September 2026 — yes, the future, we're ahead of schedule, we ate. 💅🍓

mwah, go measure some text segments. 🎀🦋✨