debug_dump(9)
π debug_dump(9) β the Kernel API Manual page, but make it make sense π«Ά
okay so bestie, we're in debug_dump(9) territory, which lives in the Kernel API Manual and is honestly kind of a vibe. it's the little function that hands you a textual representation of your debug info β or at least as much of it as actually fits in your buffer π
β¨ SYNOPSIS β¨
ssize_t debug_dump (debug_info_t *id , struct debug_view *view , char
*buf , size_t buf_size , bool reverse );
that's the whole signature, no cap. five arguments, one return value, zero drama (well, mostly).
π ARGUMENTS π
idβ the debug information you wanna use. the main character of this whole operation πviewβ the view you're dumping that debug info with. think of it as the filter/lens situation.bufβ the buffer where the textual debug data representation gets written. this is where the magic lands β¨buf_sizeβ how big that buffer is, including the trailing' 'byte. yes, including it. count it. πreverseβ go backwards from the last written entry. little reverse-chronological moment, we love to see it π¦
πΈ DESCRIPTION πΈ
so here's the tea: use this function whenever you need a textual representation of the debug information without touching an s390dbf file. like, no filesystem, no file, just vibes and a buffer. iconic honestly.
π NOTE π
bestie, it's your job β the caller's responsibility β to supply a view that's compatible with the debug information data. don't come for this function if you hand it a mismatched view, fr fr π
β RETURN β
- on success: you get the number of bytes written to the buffer β and that count does not include the trailing
' 'byte. sneaky but fair π - if
bug_size == 0, the function returns0. (yes, it's writtenbug_sizeright there in the manual β we do not edit the sacred text π«Ά) - on failure: you get an error code less than 0. sad girl hours π
π§ SEE ALSO π§
the kernel file ./arch/s390/kernel/debug.c, plus the whole friend group:
debug_next_entry(9)debug_to_act_entry(9)debug_prev_entry(9)debug_move_entry(9)debug_register_mode(9)debug_register(9)debug_register_static(9)debug_unregister(9)debug_set_level(9)debug_stop_all(9)debug_set_critical(9)debug_register_view(9)debug_unregister_view(9)
and that's the page!! mwah π it ships out of ./arch/s390/kernel, dated October 2026, and it's filed under debug_dump(9) β go forth and dump your debug info responsibly, queen ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms