PROBE::TCP.SENDMSG(3stap)

πŸ’Œ PROBE::TCP.SENDMSG.RETURN β€” from the 3stap girlies (Networking Tapset) πŸ¦‹

okay so bestie, gather round, because this one is short but it ate πŸ’… this is a page out of the SystemTap Tapset Reference, and it's all about the lil probe that fires the moment your TCP message is done being sent. not mid-send, not "oops we tried", just… done. periodt.


✨ NAME ✨

probe::tcp.sendmsg.return β€” Sending TCP message is done 🌸

like literally that's the whole vibe. the message left the building. it's gone. bye πŸ‘‹


πŸŽ€ SYNOPSIS πŸŽ€

probe tcp.sendmsg.return {}

that's it, that's the whole thing, no args, no params, just vibes and a pair of curly braces 🫢


πŸ’– VALUES πŸ’–

these are the lil facts this probe hands you when it fires, and ngl they're important so don't skip:

  • name β€” the name of this probe. iconic self-introduction energy πŸ‘‘
  • size β€” the number of bytes sent, or the error code if an error occurred. so yes bestie, read it carefully: it's either "yay we sent this many bytes" or "something went wrong and here's the code," and you do NOT get to assume which one without checking. not me being dramatic, that's just the deal 😭

🧚 CONTEXT 🧚

the context here is the process which sends a tcp message β€” so whatever process is out there doing the sending, that's who you're chilling with when this probe goes off. main character energy, truly πŸ’œ


🌈 SEE ALSO 🌈

  • tapset::tcp(3stap) β€” go read the tcp tapset page too, it's giving connected, it's giving lore, iykyk ✨

lowkey reminder: the size value is doing double duty (bytes sent or error code), so if you're out here treating it like a plain byte count every single time, that's a vibe check you will fail πŸ™ˆ

and that's the whole page, bestie!! no cap, every single detail survived the rewrite πŸ’€πŸ’– this was the SystemTap Tapset Reference, version stamped September 2026 β€” mwah, slay, go probe responsibly πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from