On Aug 8, 2011, at 11:30 AM, Wesley Bland wrote:
> The reason is because valgrind was complaining about uninitialized values that were passed into proc_get_epoch. I saw the same warnings from valgrind when I ran it. I added the code to initialize the values to what really should be the default value and the warnings went away. Since the process_name_t struct isn't an object, it doesn't have an initialization function like so many of the other objects in the code. This is what we have.
Ah, I see -- you are passing peer_name into proc_get_epoch(). I missed that.
> peer_name.jobid = ORTE_PROC_MY_NAME->jobid;
> peer_name.vpid = peer_idx;
> + peer_name.epoch = ORTE_EPOCH_INVALID;
> peer_name.epoch = orte_ess.proc_get_epoch(&peer_name);
For corporate legal information go to: