Thanks Ashley, after going through your suggestions we tried our test with
valgrind 3.3.0 and with glibc-devel-2.5-18.el5_1.1, both exhibit the same
results. A simple non-MPI test prog however returns expected responses, so
valgrind itself look ok. We then checked that the same (shared) libc get
Pak Lui wrote:
Romaric David wrote:
Pak Lui a écrit :
It was fixed at one point in the trunk before v1.3 went official, but
while rolling the code from gridengine PLM into the rsh PLM code,
this feature was left out because there was some lingering issues
that I didn't resolved and I lost
Several thins are going on here. First, this error message:
> mpirun noticed that job rank 1 with PID 9658 on node mac1 exited on signal
> 6 (Aborted).
> 2 additional processes aborted (not shown)
indicates that your application procs are aborting for some reason. The
system is then attempting to
Hi,
I've got some code that uses openmpi, and sometimes, it crashes, after
printing somthing like:
[mac1:09654] [0,0,0] ORTE_ERROR_LOG: Timeout in file
base/pls_base_orted_cmds.c at line 275
[mac1:09654] [0,0,0] ORTE_ERROR_LOG: Timeout in file pls_rsh_module.c at
line 1166
[mac1:09654] [0,0,0
On Mon, 2008-07-07 at 19:09 -0700, Tom Riddle wrote:
>
> I was attempting to get valgrind working with a simple MPI app
> (osu_latency) on OpenMPI. While it appears to report uninitialized
> values it fails to report any mallocs or frees that have been
> conducted.
The normal reason for this is
