On Di, 21.04.20 20:52, Amit anand (amit.ta...@gmail.com) wrote:
> Apr 21 16:27:16 [xxx] valgrind[4252]: valgrind: m_ume.c: can't open
> interpreter
There's something not right with the ELF interpretor in your
binaries. maybe some cross-building fuck-up? It's probably best to
ping the valgrind com
Hi,
Tried to run debug-symbol enabled systemd-udevd through valgrind.
root@[xxx]:/var/opt# vi /etc/systemd/system/.../systemd-udevd.service
ExecStart=/usr/bin/valgrind --tool=memcheck
/lib/systemd/.debug/systemd-udevd // Modified to run debug-symbol enabled
systemd.udevd binary through valgrind.
On Di, 14.04.20 20:00, Amit anand (amit.ta...@gmail.com) 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] va
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//src/basic/hashmap.c
file..
OS info : 64 bit Ubuntu OS. This is run
as guest vm.
RAM memory /swap size : 4GB RAM and
