Hi,
Am 14.06.2012 01:41, schrieb kapil anand:
I am using valgrind with callgrind tool under wine but facing a few
problems. I am using following command to run valgrind
valgrind --tool=callgrind --trace-children=yes --dump-instr=yes
--trace-jump=yes --separate-threads=yes wine program
Hi,
Here the problem that I have with valgrind-3.6.1-Debian (Ubuntu 11.10),
valgrind-3.7.0 (Ubuntu 12.04) and on SVN version:
gcc -o test MallocProblemO2.cxx
valgrind --leak-check=full ./test
No problem
If I add the -O2 flag it result in a Invalid read of 4 bytes:
gcc -O2 -o test
Dan,
On 2012-06-14, at 1:53 PM, Dan Kegel wrote:
Kevyn-Alexandre Paré kap...@rogue-research.com wrote:
==21719== Invalid read of size 4
==21719==at 0x4004F0: main (in /home/kapare/Documents/test)
==21719== Address 0x51d0044 is 4 bytes inside a block of size 6
This problem seem to be
On Thu, Jun 14, 2012 at 1:10 PM, Kevyn-Alexandre Paré
kap...@rogue-research.com wrote:
valgrind --leak-check=full --partial-loads-ok=yes ./test
Adding the flag didn't remove the error?
Are you _sure_ it is exactly the same error? Your original report
said this was the error:
==21719==
On 06/05/12 16:13, Christoph Bartoschek wrote:
So I wonder how there can be a data race for writing to data. The
memory has been just allocated and no other thread knows about it.
How can this happen?
Should have been fixed in r12629.
Bart.
Yes, i already did that (downloaded and built the tarball from the
Valgrind site) -
and now the memcpy messages have disappeared.
Thanks again
Jody
On Wed, Jun 13, 2012 at 10:04 AM, Igmar Palsenberg ig...@palsenberg.com wrote:
Thank You for the information!
I am using valgrind 3.6.1-r3
