trace_error_report_end(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– trace_error_report_end(9) πŸ’–

okay bestie, this lil page comes from the Kernel API Manual, and it's giving β€œtiny but important kernel trace moment” β€” I'm obsessed already 🫢


🌸 NAME 🌸

trace_error_report_end β€” called after printing the error report. that's the name, that's the assignment, periodt πŸ’…

✨ SYNOPSIS ✨

void trace_error_report_end (enum error_detector error_detector ,
       unsigned long id );

πŸŽ€ ARGUMENTS πŸŽ€

  • error_detector β€” short string describing the error detection tool. yes bestie, a short string, keep it cute and descriptive ✨
  • id β€” pseudo-unique descriptor identifying the report (e.g. the memory access address). it's the lil identifier for the report, and the example is literally the memory access address 🧚

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this event happens right after a debugging tool finishes printing the error report β€” literally the after-party of the error report πŸŽ‰ no cap, that's the whole moment: report printed, then this event shows up πŸ’–

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/trace/events/error_report.h β€” go peek if you want the source-y details, iykyk πŸ‘‘


mwah πŸ’‹ source/version: ./include/trace/events Β· date: October 2026 Β· page: trace_error_report_end(9)

πŸ“¦ where this page comes from