On 28/03/2023 22:58, Lennart Poettering wrote:
On Di, 28.03.23 08:13, Stephan Bergmann (sberg...@redhat.com) wrote:
* Is it guaranteed for system-run --scope that the wrapped command will run
in the surrounding process group? (Because LibreOffice' Jenkins relies on a
single process group
On 28/03/2023 08:13, Stephan Bergmann wrote:
* Is there a grammar for those --unit=X resp.
COREDUMP_USER_UNIT=X'.scope values? I noticed that at least "/" in X
gets replaced with "-" in X'.
found
<https://www.freedesktop.org/software/systemd/man/systemd.
On 27/03/2023 13:38, Lennart Poettering wrote:
another idea: can't you just wrap your tests in "systemd-run --scope
--user --name=somtestid47110815.scope" or so? we pick up unit
names in coredump handling. With that you'd run yur tests inside a
scope unit, and can then use that as key in logs+cor
On 15/03/2023 13:18, Luca Boccassi wrote:
The hard part is adding the note correctly, with the right size,
alignment, flags, etc. You can use the linker to add a placeholder
value, eg --package-metadata='{"name":"LO-testcase-"}' and
then simply edit in place before each test, as long as y
On 15/03/2023 11:29, Luca Boccassi wrote:
Use the elf metadata spec: https://systemd.io/ELF_PACKAGE_METADATA/
I need to update that, as these days it's no longer necessary to use a
custom linker script, but with binutils 2.39 (or mold 1.3.0 or lld
15.0) it's as easy as passing as a linker flag:
Hi all,
I have a question about coredumpctl core dump matching, maybe somebody
has an idea: The LibreOffice build system's `make check` machinery has
some logic to identify core files generated by crashed tests and to use
gdb to automatically obtain backtraces from them (similar to
`coredump
