On Thu, 2012-05-03 at 23:37 -0400, Zheng Da wrote:
Is this normal? Is it because my program is written in C++? How do I
suppress these errors very effectively? or these errors are actually
caused by some bugs of my program?
C++ is supported by Valgrind.
Valgrind reports some errors in glibc
hello,
==32701== Conditional jump or move depends on uninitialised value(s)
==32701==at 0x4FB3D9: fillin_rpath
(in /home/zhengda/Dropbox/research/read-test/rand-read)
==32701==by 0x4FDBCB: _dl_init_paths
(in /home/zhengda/Dropbox/research/read-test/rand-read)
==32701==by
: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] valgrind prints out a lot of error messages
pointing to the standard library
hello,
==32701== Conditional jump or move depends on uninitialised value(s)
==32701==at 0x4FB3D9: fillin_rpath
(in /home/zhengda/Dropbox/research
...@gmail.com]
*Sent:* Saturday, May 05, 2012 2:26 PM
*To:* Philippe Waroquiers
*Cc:* valgrind-users@lists.sourceforge.net
*Subject:* Re: [Valgrind-users] valgrind prints out a lot of error
messages pointing to the standard library
** **
hello,
==32701== Conditional jump or move
On Sat, 2012-05-05 at 14:45 -0400, Zheng Da wrote:
The corresponding code is shown below. I don't understand
which variable isn't initialized?
If you upgrade to Valgrind 3.7.0, you can use gdb to debug
your program under Valgrind.
With this, you have GDB monitor
On Sat, May 5, 2012 at 11:38 AM, Geoff Alexander galexand...@nc.rr.com wrote:
You don’t show the code that’s calling rand_permute::rand_permute(long,
int). In particular, the passed in value of stride could be uninitialized.
It might be even more helpful to see a small program
we can actually
Hello,
I try to use valgrind to find the memory segmentation bug in my program.
When I run it with valgrind, I get a lot of errors such as Use of
uninitialised value and Conditional jump or move depends on uninitialised
value(s). And most of errors point to some standard libraries such as
glibc
