CORE(1)

💀 CORE(1) — like, the whole vibe 💀

okay bestie, real talk: this is from the General Commands Manual, section 1, and it's about finding out what even happened to a process that died. dead process forensics, main character energy. let's go 🫶

✨ NAME ✨

core — print information about dead processes 💀✨

🎀 SYNOPSIS 🎀

core [ dir | corefile ]...

🌸 DESCRIPTION 🌸

core prints information about dead processes that have been saved as core dumps. yes. the little corpse files. and core is the forensic analyst with the tiny sunglasses. 😎💅

core reads its arguments in order. like, it literally goes one by one, no skipping, no shuffling, in order, periodt. if a directory comes up in that lineup, core reads every core file named core.* or *.core in that directory. every single one. it's thorough like that 🧚

for each core file it reads, core prints:

• the command stack file
• the date and time the core was generated 🕰️
• the command that generated it

and the stack command — if it gets run — prints a stack trace of the executing thread at the time of the core dump. see db(1) for that one, iykyk 🔥

ok now the part where you don't have to type anything at all: if no arguments are given, core searches the directory $COREDIR for core files. and if $COREDIR is not set, it searches the current directory. so it just. finds them. on its own. iconic behavior honestly 👑

🦋 SOURCE 🦋

/src/cmd/core.c

🌈 SEE ALSO 🌈

• acid(1)
• db(1)
• core(5)

and that's the whole thing, bestie — go read some dead processes, you got this 💖✨

🎀 sign-off: this was page CORE(1) from the General Commands Manual, and the source lives at /src/cmd/core.c — that's the whole footer, no cap. bye bye!! 🦋🌸💜