debug_text_event(9)

💖 debug_text_event(9) 💖

okay so bestie, welcome to the debug_text_event(9) page — yes that's the manual name, we're being fancy today ✨ this one's from the Kernel API Manual and it's literally all about writing a plain string into your debug log. ascii vibes only 💅

---

🌸 NAME 🌸

debug_text_event — writes a string debug entry in ascii format to the active debug area (but only if level <= the actual debug level, okurrr 🎀)

---

✨ SYNOPSIS ✨

debug_entry_t * debug_text_event (debug_info_t *id , int level , const
char *txt );

---

🫶 ARGUMENTS 🫶

• id — the handle for your debug log. your main character pointer, basically 👑
• level — the debug level. this is the vibe check 🔥
• txt — the string that goes into the debug entry. the actual content, the moment, the lore 🦋

---

💫 RETURN 💫

• Address of the written debug entry — slay, it worked 💖
• NULL if there's an error — sad but true, no cap 😭

---

🌈 SEE ALSO 🌈

kernel file ./arch/s390/include/asm/debug.h, plus the whole friend group:

• debug_level_enabled(9)
• debug_event(9)
• debug_int_event(9)
• debug_long_event(9)
• debug_sprintf_event(9)
• debug_exception(9)
• debug_int_exception(9)
• debug_long_exception(9)
• debug_text_exception(9)
• debug_sprintf_exception(9)
• DEFINE_STATIC_DEBUG_INFO(9)

---

ngl bestie, the whole crew is listed above — go say hi to the exception girlies too, they're iconic 🙈

---

and that's the whole page!! 🧚 this lil drop comes from ./arch/s390/include/asm and it's dated October 2026 — so like, future-coded of it ⭐ anyway ily, go log some strings, and remember: only if the level passes the vibe check 💜💅🍓