BTW, the -1 file has an invalid free in it that we just fixed. That's not part of the epoch value issue, of course. :-)
On Aug 5, 2011, at 3:03 PM, Jeff Squyres wrote: > Ralph and I are trying to track down the mysterious ORTE error. > > In doing so, I have found at least one fairly repeatable error on my cluster: > when running through SLURM the ibm/dynamic/spawn test, where we mpirun 3 > procs and then we MPI_COMM_SPAWN 3 more. Running the orteds through > valgrind, I see a bunch of uninitialized epoch issues. > > Attached at the 2 valgrind outputs. > > Can these be fixed? I don't know if they're actual problems or not, but > seeing uninitialized values go by makes me extremely nervous. > > Thanks! > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > <valgrind-orted-1.txt><valgrind-orted-2.txt>_______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
