Hello,
I'm trying to use valgrind do debug an mpich2 program. Unfortunately, I get the
following error:
libmpi.so.0: cannot open shared object file: No such file or directory
I found out that libmpich.so.1.0 should be linked to instead (see
libmpiwrap.c). Valgrind documation states that The
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 a snapshot of a program under Valgrind, kinda similar to the way
a fork() clones the process space, and then continue again from that
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
Am 05.05.2012 16:38, schrieb Philippe Waroquiers:
On Sat, 2012-05-05 at 14:25 +0200, Martin Kalany wrote:
Hello,
I'm trying to use valgrind do debug an mpich2 program. Unfortunately, I get
the following error:
libmpi.so.0: cannot open shared object file: No such file or directory
I
On Sat, 2012-05-05 at 14:25 +0200, Martin Kalany wrote:
Hello,
I'm trying to use valgrind do debug an mpich2 program. Unfortunately, I get
the following error:
libmpi.so.0: cannot open shared object file: No such file or directory
I found out that libmpich.so.1.0 should be linked to
On Sat, 2012-05-05 at 18:14 +0200, Martin Kalany wrote:
Is the 'cannot open' error only there when running under Valgrind ?
Yes. When I use mpirun, it's fine.
What I think is strange that valgrind apperantly tries to load
libmpi.so, although it should load libmpich.so.1.0
Maybe a
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
Da,
You dont show the code thats calling rand_permute::rand_permute(long,
int). In particular, the passed in value of stride could be uninitialized.
Geoff
-Original Message-
From: Zheng Da [mailto:zhengda1...@gmail.com]
Sent: Saturday, May 05, 2012 2:26 PM
To: Philippe Waroquiers
Cc:
157 class global_rand_permute_workload: public workload_gen
158 {
159 long start;
160 long end;
161 static const rand_permute *permute;
162 public:
163 global_rand_permute_workload(long num, int stride, long start, long
end) {
164 if (permute == NULL) {
165
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
On Sun, 2012-05-06 at 00:24 +0200, Martin Kalany wrote:
Valgrind documation states that The MPI functions to be wrapped are assumed
to be in an ELF shared object with soname matching libmpi.so*. This is
knownto be correct at least for Open MPI and Quadrics MPI, and can easily
be changed if
12 matches
Mail list logo
