Remember: we have the OMPI teleconf tomorrow at 11am US Eastern, which is still
a "different" time in Europe this week. Next Tuesday, we should be back to the
"normal" European time.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_
There's a bunch of pending CMRs that don't have reviews. I pinged each ticket
telling each ticket owner that they need a reviewer before it will be approved.
Please check your tickets; thanks.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/ab
Hello @ll.
I'm having a problem when i try to access to data->procs->addr[vpid] when
the vpid belong to a recently killed process. I'm sending here a piece of my
code. The problem is that the execution is always entering in the last if
clause maybe because the information of the dead process is no
You should never access a pointer array's data area that way (i.e., by index
against the raw data). You really should do:
if (NULL == (proc = (orte_proc_t*)opal_pointer_array_get_item(jdata->procs,
vpid))) {
/* error report */
}
to protect against changes. The errmgr generally doesn't rem
If MPI_Probe() encounters an error causing it to exit with the
'status.MPI_ERROR' set, say:
ret = MPI_Probe(MPI_ANY_SOURCE, MPI_ANY_TAG, MPI_COMM_WORLD, &status);
Should it return an error? So should it return:
- ret = status.MPI_ERROR
- ret = MPI_ERROR_IN_STATUS
- ret = MPI_SUCCESS
Addition
Thanks Ralph for your reply.
2011/3/21 Ralph Castain
> You should never access a pointer array's data area that way (i.e., by
> index against the raw data). You really should do:
>
> if (NULL == (proc = (orte_proc_t*)opal_pointer_array_get_item(jdata->procs,
> vpid))) {
> /* error report *
On Mar 21, 2011, at 2:51 PM, Hugo Meyer wrote:
> Thanks Ralph for your reply.
>
> 2011/3/21 Ralph Castain
> You should never access a pointer array's data area that way (i.e., by index
> against the raw data). You really should do:
>
> if (NULL == (proc = (orte_proc_t*)opal_pointer_array_get_
Josh,
If we don't take in account resilience I would not expect MPI_Probe to have
that many opportunities to return errors. However, in order to keep the
implementation consistent (with the other MPI functions) I would abide to the
following.
MPI_ERROR_IN_STATUS is only for calls taking multip
