shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-22 13:33:56 +03:00
Code

docs/COREDUMP_PACKAGE_METADATA: ELF section should be allocated and 0-padded

Browse Source
This commit is contained in:
Luca Boccassi 2021-10-27 11:27:50 +01:00 committed by Zbigniew Jędrzejewski-Szmek
parent 3f9335e8e3
commit f3f1172cf6
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/COREDUMP_PACKAGE_METADATA.md
View File

@ -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.