Re: [Valgrind-users] SfMayBlock with fuse-compatible

2016-12-07 13:54 GMT+01:00 Radoslaw Kujawa : > Hi Ivo, > > here is the log that appeared when we switched on trace-syscalls: > > SYSCALL[28094,1](89) sys_readlink ( 0x374581b667(/proc/self/exe), > 0xffeffec10, 4096 ) --> [pre-success] Success(0x52) > valgrind: m_syswrap/syswrap-main.c:1938 (vgPlai

Re: [Valgrind-users] How to Valgrind processes near 256GB?

2016-12-07 18:39 GMT+01:00 Gregory Czajkowski : > I have processes near 256GB, need to run valgrind to determine why, but it > runs out of memory ~60GB > > > ==15336== Valgrind's memory management: out of memory: > > ==15336==newSuperblock's request for 4194304 bytes failed. > > ==1533

Re: [Valgrind-users] SfMayBlock with fuse-compatible

W dniu 08.12.2016 o 11:12, Ivo Raisr pisze: 2016-12-07 13:54 GMT+01:00 Radoslaw Kujawa >: Hi Ivo, here is the log that appeared when we switched on trace-syscalls: SYSCALL[28094,1](89) sys_readlink ( 0x374581b667(/proc/self/exe), 0xffeffec10, 4

[Valgrind-users] Valgrind crash on armv7l

Hi,   I have an embedded linux system similar to the BeagleBone. It runs buildroot on it.   # uname -a   Linux xenon 4.4.21 #1 PREEMPT Thu Dec 8 12:19:53 CET 2016 armv7l GNU/Linux   Within the last days, I enabled valgrind in buildroot (version 3.11.0) to examine memory issues in some programs.

Re: [Valgrind-users] Valgrind crash on armv7l

> Most of the time, when I start valgrind like this: > # valgrind --tool=memcheck > it exits with a segmentation fault. I tried different programs, small and > big, but this does not really seem to make a difference. ... Most of the time? Then run valgrind under gdb, get the traceback at the

Re: [Valgrind-users] SfMayBlock with fuse-compatible

2016-12-08 11:28 GMT+01:00 Radoslaw Kujawa : > > W dniu 08.12.2016 o 11:12, Ivo Raisr pisze: > > > > 2016-12-07 13:54 GMT+01:00 Radoslaw Kujawa : > >> Hi Ivo, >> >> here is the log that appeared when we switched on trace-syscalls: >> >> SYSCALL[28094,1](89) sys_readlink ( 0x374581b667(/proc/self/e