Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-11-06 20:49:12


On Nov 6, 2007, at 4:42 AM, Åke Sandgren wrote:

> I had the same problem with pathscale.

There is a known outstanding problem with the pathscale problem. I am
still waiting for a solution from their engineers (we don't know yet
whether it's an OMPI issue or a Pathscale issue, but my [biased] money
is on a Pathscale issue :-) -- it doesn't happen with any other
compiler).

> Try this, i think it is the solution i found.
>
> diff -ru site/opal/runtime/opal_init.c
> amd64_ubuntu606-psc/opal/runtime/opal_init.c
> --- site/opal/runtime/opal_init.c 2007-10-20 03:00:35.000000000
> +0200
> +++ amd64_ubuntu606-psc/opal/runtime/opal_init.c 2007-10-23
> 16:12:15.000000000 +0200
> @@ -169,7 +169,7 @@
> }
>
> /* register params for opal */
> - if (OPAL_SUCCESS != opal_register_params()) {
> + if (OPAL_SUCCESS != (ret = opal_register_params())) {
> error = "opal_register_params";
> goto return_error;
> }

I don't see why this change would make any difference in terms of a
segv...?

I see that ret is an uninitialized variable in the error case (which
I'll fix -- thanks for pointing it out :-) ) -- but I don't see how
that would fix a segv. Am I missing something?

-- 
Jeff Squyres
Cisco Systems