Yes.
That was the problem Ralph. Again, thanks a lot for your help, it was a
silly mistake of mine :).
Best regards.
Hugo Meyer
2011/3/22 Ralph Castain
> The problem is here:
>
> /* Pack the faulty vpid */
> if (ORT
The problem is here:
/* Pack the faulty vpid */
if (ORTE_SUCCESS != (rc =
opal_dss.pack(buffer, &proc, 1, ORTE_NAME))) {
ORTE_ERROR_LOG(rc);
Thanks again Ralph for your reply.
> There's your problem - that module is run in the daemon, where the
> orte_job_data pointer array isn't used. You have to use the
> orte_local_jobdata and orte_local_children lists instead. So once the HNP
> replies with the jobid, you look up the orte_odls_job
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_
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 *
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
