[systemd-devel] Not able to get valgrind profiling output 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 in file
https://github.com/systemd/systemd/blob/<branch>/src/basic/hashmap.c
file..

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.

Followed steps mentioned in URL
"https://lists.freedesktop.org/archives/systemd-devel/2020-April/044367.html"
to start systemd-udevd.service in valgrind.


Could see few lines of valgrind output with "systemctl status
systemd-udev.service" command

Below information displayed on console.

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.

Initial few lines (7-8 lines) of valgrind profiling output is available.

Can you please let me know if there is any other way or tool available
to identify how memory allocation and release done in
systemd-udevd.service.


Thanks,
Amit