ERROR::REPORTING(7stap)

✨ ERROR::REPORTING ✨

ok so bestie, welcome to error::reporting from the 7stap manual section 💖 this is the page that tells you what to do when systemtap is being a little drama queen and something breaks. it's all about systemtap error reporting — where to go, who to tell, and what receipts to bring. 🎀

💌 COMMERCIAL SUPPORT

okay so first things first. if you've got a commercial support agreement with your OS distributor and it covers this software, then girllll use their problem reporting systems first. get your money's worth, you literally paid for it. 💅

🫶 COMMUNITY SUPPORT

now for the rest of us — the systemtap community and its volunteer devs are so eager to hear your problem reports, because that's literally how they make the software better. they want your bug reports like we want iced coffee. 🧊

here are all the ways to slide into their DMs (respectfully):

• public mailing list — systemtap@sourceware.org
• public IRC — #systemtap on irc.oftc.net, and use fpaste.org for snippets of text
• public bugzilla — http://sourceware.org/bugzilla/

not me giving you three whole ways to reach out. pick your fave, they're all valid. 🌈

🔍 INFORMATION TO COLLECT

bestie, when you report, don't be mysterious. in general, please include info about:

• your platform
• your systemtap version
• your scripts & custom tapsets
• your systemtap invocation
• the actual behavior / errors you saw
• the expected behavior

and here's the iconic part: the stap-report script collects all that useful system/kernel information that helps describe your OS environment. so please include its output too. it's giving "here's everything you need, no follow-up questions." 👑

👀 SEE ALSO

• stap(1)
• stap-report(1)
• http://sourceware.org/systemtap/wiki/

and that's the whole vibe, bestie 💜 this was ERROR::REPORTING(7stap), coming at you from the 7stap manual, part of the systemtap docs. go forth and report your bugs beautifully. slay. ✨🦋🌸