Hi,
the possible fixes (that worked for me every time) are mentioned at the
bottom of the output:
valgrind: Possible fixes: (1, short term): install glibc's debuginfo
valgrind: package on this machine. (2, longer term): ask the packagers
valgrind: for your Linux distribution to please in
Hello Phillipe,
thank you for your response. I think you gave me an idea.
// Oliver
On 2012-05-05 14:22, Philippe Waroquiers wrote:
On Fri, 2012-05-04 at 17:32 +, Oliver Schneider wrote:
Hi folks,
I've got a question about Valgrind and its Memcheck tool. Is it possible
to take
Hi folks,
I've got a question about Valgrind and its Memcheck tool. Is it possible
to take a snapshot of a program under Valgrind, kinda similar to the way
a fork() clones the process space, and then continue again from that
snapshot with Valgrind? Could fork() perhaps be the answer?
Basically
On 2011-01-21 08:59, Stutz Oliver wrote:
There is not much in the Net about AIX-Valgrind but i have found posts from
people who claim that 3.3.0/1 runs.
The ./configure works Properly for me... but here i get stuck, the question
is why is that, i have no clue what the -C stands for
Hello,
maybe someone can tell me whether my little shell snippet is based on
the right assumptions in order to find the Valgrind version:
valgrind --version|sed 's/valgrind-//g;s/\([0-9]*\.[0-9]\)\..*/\1/'
Can one rely on the format of the string being
valgrind-x.y.z[whatever] (where x.y are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
from my experience you can ignore such supposed leaks. I think it has to
do with the way the process gets torn down when certain signals reach it.
// Oliver
PS: Sorry, had it sent to the OP directly.
On 2010-07-30 12:46, Peyush Kumar wrote:
Hi,
I noticed that Ubuntu 10.04 now contains a Valgrind version dubbed
Valgrind-3.6.0.SVN-Debian and that when I run my code under it, I get:
Valgrind: fatal error - cannot continue: use of the deprecated
client requests VG_USERREQ__PRINTF or VG_USERREQ__PRINTF_BACKTRACE
on a platform where they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there,
looking over the options in memcheck I fail to find one that will
immediately issue an error as soon as I copy uninitialized memory. E.g.
I have a buffer (const char* buf) bigger than the data I read, so only n
Bytes out of n+m Bytes have
a define as literal string. This way it would be easier to
acknowledge you.
Furthermore I'd like to know whether the headers will differ between
platforms, depending on which platform I install them (from the tarball).
Thanks in advance,
- --
Oliver Schneider
Researcher / Developer
FRISK Software
Hello and thanks first of all for your detailed reply.
What is the goal in integrating Valgrind with this scheme; that is,
what is not happening now which should be?
For example checking whether the allocation function and its
counter-part use the same tag. I thought it would be better to
Hi,
several systems use tagged memory to identify blocks of memory used by
the same code and similar. What would be the best way of telling
Valgrind about this custom allocation scheme? The Memory Pools don't
seem to cover the possibility of tagged memory, as they only take
parameters similar
Hello everybody,
I've been trying to build Valgrind on my Debian (5.0.3) box, since the
--read-var-info option doesn't seem to be in the version that comes via
APT (which identifies as valgrind-3.3.1-Debian).
Running ./configure --prefix=$HOME/bin doesn't give any errors, but
once I start
directory was the correct one ...
But it's beyond me why cd failed. Anyway, perhaps this line above (no
line breaks, though) will help others having similar issues (remember to
call ./configure after it, though) ...
// Oliver
On 2010-02-16 20:24, Oliver Schneider wrote:
Hello everybody
13 matches
Mail list logo
