[systemd-devel] OS shutting down after starting systemd-udevd.service through valgrind

[Amit anand]

Hi,
I am trying to run systemd-udevd.service through valgrind for debugging
some memory corruption issue.

OS info                             :  64 bit Ubuntu OS. This is run as
guest vm.
RAM memory /swap size : 4GB RAM and 3 GB SWAP space.
systemd version               : systemd v237.

The command uname -a gives below result.
Linux [xxx] 4.14.147-yocto-standard #1 SMP PREEMPT Thu Jan 30 18:52:38 UTC
2020 x86_64 GNU/Linux
note : [xxx] is masked text.

Referred to link
*https://lists.freedesktop.org/archives/systemd-devel/2015-April/030086.html
<https://lists.freedesktop.org/archives/systemd-devel/2015-April/030086.html>*
.
Followed below steps to run systemd-udev.service through valgrind.

*step 1* :
On terminal, command "systemctl edit --full systemd-udev.service"

Prefixed it's ExecStart= parameter with an invocation of valgrind as below,
ExecStart=/usr/bin/valgrind --tool=memcheck /lib/systemd/systemd-udevd

*Step 2* :
On terminal, command "systemctl daemon-reload"

Step 3 :
On terminal, command "systemctl restart systemd-udevd"

Step 4 :
On terminal, command ps command gave below result for udevd.
[[0;1;32m●[[0m systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/etc/systemd/system/systemd-udevd.service; enabled;
vendor preset: enabled)
   Active: [[0;1;32mactive (running)[[0m since Fri 2020-04-03 14:40:41 UTC;
9s ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
 Main PID: 13179 (memcheck-amd64-)
   Status: "Processing with 16 children at max"
   Memory: 42.6M
   CGroup: /system.slice/systemd-udevd.service
           └─13179 /usr/bin/valgrind --tool=memcheck
/lib/systemd/systemd-udevd


Step 5 : Could see few lines of valgrind output with "systemctl status
systemd-udev.service" command
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x4012BD1: ??? (in
/lib/ld-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x5BFCC8B:
_dl_catch_exception (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x4012789: ??? (in
/lib/ld-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x5BFC2DC: ??? (in
/lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x5BFCC8B:
_dl_catch_exception (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x5BFCCFE:
_dl_catch_error (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x5BFC3A6: ??? (in
/lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==    by 0x5BFC436:
__libc_dlopen_mode (in /lib/libc-2.27.so)
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==  Address 0x650b1c0 is 16
bytes after a block of size 32 in arena "client"
Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==

Note : [xxx] is masked text.

However, guest vm (Ubuntu OS) shut down within 2 minutes of restarting
systemd-udevd service.
Attempt to reboot the guest vm ( Ubuntu OS) failed.

Can you please guide/suggest how to prevent the Ubuntu OS from shutting
down after restarting systemd-udevd.service with valgrind.

Thanks,
Amit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20200403/a5dd6e2d/attachment-0001.htm>