debug_exception(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

hey bestie, welcome to debug_exception(9) from the Kernel API Manual β€” the page for writing a binary debug entry and moving on to the next debug area. πŸ’…

πŸ’– NAME πŸ’–

debug_exception β€” writes a binary debug entry to the active debug area (if level <= actual debug level) and switches to the next debug area.

Okay so it’s literally giving β€œlog this binary debug entry into the active debug area when the level condition is true, then bounce to the next debug area.” ✨

✨ SYNOPSIS ✨

debug_entry_t * debug_exception (debug_info_t *id , int level , void
       *data , int length );

πŸŽ€ ARGUMENTS πŸŽ€

  • id β€” handle for debug log. 🫢
  • level β€” debug level. 🌈
  • data β€” pointer to data for debug entry. πŸ“
  • length β€” length of data in bytes. πŸ“

🌸 RETURN 🌸

  • Address of written debug entry πŸ‘‘
  • NULL if error πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./arch/s390/include/asm/debug.h is where the lore lives, bestie. Also check out: debug_level_enabled(9), debug_event(9), debug_int_event(9), debug_long_event(9), debug_text_event(9), debug_sprintf_event(9), debug_int_exception(9), debug_long_exception(9), debug_text_exception(9), debug_sprintf_exception(9), DEFINE_STATIC_DEBUG_INFO(9). Go off, icon. πŸ’œ


mwah πŸ’‹ β€” source spot: ./arch/s390/include/asm, date: October 2026. bye bestie! πŸŽ€

πŸ“¦ where this page comes from