[valgrind] [Bug 464184] New: readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464184
Bug ID: 464184
Summary: readlink("/proc/self/exe") failed when debug
systemd(pid 1)
Classification: Developer tools
Product: valgrind
Version: 3.16.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: heng@windriver.com
Target Milestone: ---
SUMMARY
By the https://github.com/systemd/systemd/issues/2187, I try to debug systemd
(pid 1) memory leak using valgrind.
Kernel boot command is below:
/usr/bin/valgrind --leak-check=full --log-file=/valgrind.out
/lib/systemd/systemd
Boot log and result of "/usr/bin/valgrind /lib/systemd/systemd"
OBSERVED RESULT
[ 11.653187] /usr/bin/valgrind --leak-check=full --log-file=/valgrind.out
/lib/systemd/systemdsh: cannot set terminal process group (-1): Inappropriate
ioctl for device
sh: no job control in this shell
sh-4.3# /usr/bin/valgrind /lib/systemd/systemd
valgrind: warning (non-fatal): readlink("/proc/self/exe") failed.
valgrind: continuing, however --trace-children=yes will not work.
--247:0: aspacem Valgrind: FATAL: can't open /proc/self/maps
--247:0: aspacem Exiting now.
EXPECTED RESULT
In this link https://github.com/systemd/systemd/issues/2187, valgrind can debug
systemd(pid 1)
SOFTWARE/OS VERSIONS
Linux: 2.6 or yocto dunfell
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 464185] New: readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185
Bug ID: 464185
Summary: readlink("/proc/self/exe") failed when debug
systemd(pid 1)
Classification: Developer tools
Product: valgrind
Version: 3.16.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: heng@windriver.com
Target Milestone: ---
SUMMARY
By the https://github.com/systemd/systemd/issues/2187, I try to debug systemd
(pid 1) memory leak using valgrind.
Kernel boot command is below:
/usr/bin/valgrind --leak-check=full --log-file=/valgrind.out
/lib/systemd/systemd
Boot log and result of "/usr/bin/valgrind /lib/systemd/systemd"
OBSERVED RESULT
[ 11.653187] /usr/bin/valgrind --leak-check=full --log-file=/valgrind.out
/lib/systemd/systemdsh: cannot set terminal process group (-1): Inappropriate
ioctl for device
sh: no job control in this shell
sh-4.3# /usr/bin/valgrind /lib/systemd/systemd
valgrind: warning (non-fatal): readlink("/proc/self/exe") failed.
valgrind: continuing, however --trace-children=yes will not work.
--247:0: aspacem Valgrind: FATAL: can't open /proc/self/maps
--247:0: aspacem Exiting now.
EXPECTED RESULT
In this link https://github.com/systemd/systemd/issues/2187, valgrind can debug
systemd(pid 1)
SOFTWARE/OS VERSIONS
Linux: 2.6 or yocto dunfell
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185 --- Comment #1 from hguo3 --- Is there anything missing in my valgrind? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185 --- Comment #4 from hguo3 --- Thanks for reply and will ask systemd for help. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185
--- Comment #5 from hguo3 ---
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.
[valgrind] [Bug 464185] readlink("/proc/self/exe") failed when debug systemd(pid 1)
https://bugs.kde.org/show_bug.cgi?id=464185 --- Comment #7 from hguo3 --- https://github.com/systemd/systemd/issues/26046 Our systemd version is too old to support by upstream. -- You are receiving this mail because: You are watching all bug changes.
