https://bugs.kde.org/show_bug.cgi?id=464185
--- Comment #5 from hguo3 <heng....@windriver.com> ---
Get below debug log, when I use "valgrind -d". It is valgrind exit before
systemd runs. Seems this is valgrind issue not systemd
------------------------------------------------
sh-4.3#/usr/bin/valgrind -d --leak-check=full --log-file=/valgrind.out
/lib/systemd/systemd
--254:1:debuglog DebugLog system started by Stage 1, level 1 logging requested
--254:1:launcher no tool requested, defaulting to 'memcheck'
--254:1:launcher selected platform 'ppc64be-linux'
valgrind: warning (non-fatal): readlink("/proc/self/exe") failed.
valgrind: continuing, however --trace-children=yes will not work.
--254:1:launcher launching /usr/lib64/valgrind/memcheck-ppc64be-linux
--254:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging
requested
--254:1: main Welcome to Valgrind version 3.16.1 debug logging
--254:1: main Checking current stack is plausible
--254:1: main Checking initial stack was noted
--254:1: main Starting the address space manager
--254:0: aspacem Valgrind: FATAL: can't open /proc/self/maps
--254:0: aspacem Exiting now.
sh-4.3#
--
You are receiving this mail because:
You are watching all bug changes.
