From ff2ce8dc9ccc699704329fe7aadd9e6eed4df0a2 Mon Sep 17 00:00:00 2001 From: Andrew Halaney Date: Mon, 26 Oct 2026 15:02:11 -0500 Subject: [PATCH] man: document COREDUMP_TID= and COREDUMP_THREAD_NAME= These journal fields and the matching user.coredump.tid and user.coredump.thread_name xattrs were added in v261 by 4c7af7d9d1 ("coredump: capture crashing thread ID and name"), but never documented. --- man/systemd-coredump.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml index 891edd1fe94..30b67055df9 100644 --- a/man/systemd-coredump.xml +++ b/man/systemd-coredump.xml @@ -416,6 +416,19 @@ COREDUMP_FILENAME=/var/lib/systemd/coredump/core.Web….552351.….zst + + COREDUMP_TID= + COREDUMP_THREAD_NAME= + The thread number (TID) and name + (/proc/pid/task/tid/comm) + of the thread that triggered the core dump. For single-threaded processes the TID is the same as + the PID. Like COREDUMP_PID=, the TID is the value as seen in the namespace where + systemd-coredump is running. + + + + + COREDUMP_BY_PIDFD= If the crashed process was analyzed using a PIDFD provided by the kernel (requires @@ -725,6 +738,16 @@ flags: ... + + + user.coredump.tid + user.coredump.thread_name + + Those are the same as COREDUMP_TID= and + COREDUMP_THREAD_NAME=, described above. + + + Those can be viewed using