From: Luca Boccassi Date: Wed, 27 Oct 2021 10:27:50 +0000 (+0100) Subject: docs/COREDUMP_PACKAGE_METADATA: ELF section should be allocated and 0-padded X-Git-Tag: v250-rc1~414 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f3f1172cf6302cffbffe93f2c21323348c33938f;p=thirdparty%2Fsystemd.git docs/COREDUMP_PACKAGE_METADATA: ELF section should be allocated and 0-padded --- diff --git a/docs/COREDUMP_PACKAGE_METADATA.md b/docs/COREDUMP_PACKAGE_METADATA.md index fbbba1464c2..e34abbd1478 100644 --- a/docs/COREDUMP_PACKAGE_METADATA.md +++ b/docs/COREDUMP_PACKAGE_METADATA.md @@ -33,12 +33,12 @@ This document will attempt to define a common metadata format specification, so multiple implementers might use it when building packages, or core file analyzers, and so on. -The metadata will be embedded in a single, new, 4-bytes-aligned, read-only ELF header section, -in a key-value JSON format. Implementers working on parsing core files should not assume a -specific list of keys, but parse anything that is included in the section. -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. +The metadata will be embedded in a single, new, 4-bytes-aligned, allocated, 0-padded, +read-only ELF header section, in a key-value JSON format. Implementers working on parsing +core files should not assume a specific list of keys, but parse anything that is included +in the section. 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.