include/trace/events/coredump.h
Source file repositories/reference/linux-study-clean/include/trace/events/coredump.h
File Facts
- System
- Linux kernel
- Corpus path
include/trace/events/coredump.h- Extension
.h- Size
- 1010 bytes
- Lines
- 46
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
Dependency Surface
linux/sched.hlinux/tracepoint.htrace/define_trace.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#undef TRACE_SYSTEM
#define TRACE_SYSTEM coredump
#if !defined(_TRACE_COREDUMP_H) || defined(TRACE_HEADER_MULTI_READ)
#define _TRACE_COREDUMP_H
#include <linux/sched.h>
#include <linux/tracepoint.h>
/**
* coredump - called when a coredump starts
* @sig: signal number that triggered the coredump
*
* This tracepoint fires at the beginning of a coredump attempt,
* providing a stable interface for monitoring coredump events.
*/
TRACE_EVENT(coredump,
TP_PROTO(int sig),
TP_ARGS(sig),
TP_STRUCT__entry(
__field(int, sig)
__array(char, comm, TASK_COMM_LEN)
),
TP_fast_assign(
__entry->sig = sig;
memcpy(__entry->comm, current->comm, TASK_COMM_LEN);
),
TP_printk("sig=%d comm=%s",
__entry->sig, __entry->comm)
);
#endif /* _TRACE_COREDUMP_H */
/* This part must be outside protection */
#include <trace/define_trace.h>
Annotation
- Immediate include surface: `linux/sched.h`, `linux/tracepoint.h`, `trace/define_trace.h`.
- Atlas domain: Repository Root And Misc / include.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.