Re: Not able to get valgrind profiling output after starting systemd-udevd.service through valgrind.

[Lennart Poettering <mzerqung@xxxxxxxxxxx>]

On Di, 14.04.20 20:00, Amit anand (amit.table@xxxxxxxxx) wrote:

> 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==

To be truly useful you need to enable debug symbols in your builds, so
that valgrind can show you something for useful than pointer values.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel