picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

README: note that installing valgrind-devel maybe useful to developers (#6502) 

Commit also mentions that when running under valgrind we actually don't
execve() systemd-shutdown. We have a comment about this in the code, but
being upfront about this change in behavior doesn't hurt.
This commit is contained in:
Michal Sekletar 2017-08-30 13:07:43 +02:00 committed by Lennart Poettering
parent f8d8c6bc90
commit 7817154d5a
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README
View File

@ -291,9 +291,12 @@ WARNINGS:
https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
To run systemd under valgrind, compile with VALGRIND defined To run systemd under valgrind, compile with VALGRIND defined
(e.g. ./configure CPPFLAGS='... -DVALGRIND=1'). Otherwise, (e.g. CPPFLAGS='... -DVALGRIND=1' meson <options>) and have valgrind
false positives will be triggered by code which violates development headers installed (i.e. valgrind-devel or
some rules but is actually safe. equivalent). Otherwise, false positives will be triggered by code which
violates some rules but is actually safe. Note that valgrind generates
nice output only on exit(), hence on shutdown we don't execve()
systemd-shutdown.
ENGINEERING AND CONSULTING SERVICES: ENGINEERING AND CONSULTING SERVICES:
Kinvolk (https://kinvolk.io) offers professional engineering Kinvolk (https://kinvolk.io) offers professional engineering