PROBE::SIGNAL.FORC(3stap)

πŸ’₯ probe::signal.force_segv πŸ’₯

okay bestie, welcome to the Signal Tapset corner of the SystemTap reference πŸ’… this one's a probe point page from the <hotpink>PROBE::SIGNAL.FORC(3stap)</hotpink> manual, and yes the name is literally force_segv, it's giving drama and we love that for it.


✨ NAME ✨

probe::signal.force_segv β€” forcing the send of SIGSEGV 🫢

like, somebody's about to get a segmentation fault and it was not an accident. no cap.


πŸŽ€ SYNOPSIS πŸŽ€

probe signal.force_segv {}

that's it. that's the whole synopsis. she's minimal, she's mysterious, she ate πŸ’…


🌸 VALUES 🌸

every probe point in this tapset comes with a little gift bag of variables, and here's what's inside yours 🎁

  • sig β€” the number of the signal πŸ”’
  • name β€” the name of the probe point 🏷️
  • sig_name β€” a string representation of the signal, so like the cute readable version instead of just a number ✨
  • pid_name β€” the name of the process that's receiving the signal πŸ‘€
  • sig_pid β€” the PID of the process receiving the signal πŸ†”
not me listing all five like they're my five personality traits 😭 but fr fr, if you're writing a script and you need to know who got the signal and what the signal was, this is your moment.

πŸ¦‹ SEE ALSO πŸ¦‹

  • tapset::signal(3stap) β€” go read the main signal tapset page, she's the blueprint, the mother, the icon πŸ‘‘

okay that's the whole page, you're basically a SystemTap signal girlie now πŸ’œ

this was brought to you by the SystemTap Tapset Reference, version vibes of September 2026 β€” stay slaying, stay probing, and may your SIGSEGVs always be on purpose πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from