diff options
| author | Michal Sekletar <msekletar@users.noreply.github.com> | 2017-08-30 13:07:43 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2017-08-30 13:07:43 +0200 |
| commit | 7817154d5ac1c54b23d0a6a858e00c5cdb00d37d (patch) | |
| tree | 5ff35cdf6efbc96e1f43689c00b07c74715baf9d /README | |
| parent | f8d8c6bc90ab51b5d7bb90676345fd45191ba238 (diff) | |
| download | systemd-7817154d5ac1c54b23d0a6a858e00c5cdb00d37d.tar.gz | |
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.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 9 |
1 files changed, 6 insertions, 3 deletions
@@ -291,9 +291,12 @@ WARNINGS: https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken To run systemd under valgrind, compile with VALGRIND defined - (e.g. ./configure CPPFLAGS='... -DVALGRIND=1'). Otherwise, - false positives will be triggered by code which violates - some rules but is actually safe. + (e.g. CPPFLAGS='... -DVALGRIND=1' meson <options>) and have valgrind + development headers installed (i.e. valgrind-devel or + 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: Kinvolk (https://kinvolk.io) offers professional engineering |