From 4f90b052e5a643884ae2d78d99940b818605752f Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 6 May 2021 03:05:02 +0200 Subject: [PATCH] docs/COREDUMP_PACKAGE_METADATA.md: Add debuginfod key Signed-off-by: Mark Wielaard --- docs/COREDUMP_PACKAGE_METADATA.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/COREDUMP_PACKAGE_METADATA.md b/docs/COREDUMP_PACKAGE_METADATA.md index ab7c4596de..6ef746f246 100644 --- a/docs/COREDUMP_PACKAGE_METADATA.md +++ b/docs/COREDUMP_PACKAGE_METADATA.md @@ -39,6 +39,9 @@ Implementers working on build tools should strive to use the same key names, for consistency. The most common will be listed here. When corresponding to the content of os-release, the values should match, again for consistency. +If available, the metadata should also include the debuginfod server URL that can provide +the original executable, debuginfo and sources, to further facilitate debugging. + * Section header ``` @@ -58,6 +61,7 @@ Value: a JSON string with the structure described below "name":"coreutils", "version": "4711.0815.fc13.arm32", "osCpe": # A CPE name for the operating system, `CPE_NAME` from os-release is a good default + "debugInfoUrl": "https://debuginfod.fedoraproject.org/", } ```