Paul and all,
before r32408, the environment/abort test from the ibm test suite
crashed with SIGSEGV.
there is no more crash after the fix :-)
that being said, i experience some (random) hangs on my VM :
--mca btl tcp,self => no hang
--mca btl sm,self or --mca btl vader,self => hang about 25% of
Paul,
i confirm ampersand was missing and this was a bug
/* a similar bug was fixed by Ralph in r32357 */
i commited r32408 in order to fix these three bugs.
i also took the liberty to replace the OMPI_CAST_RTE_NAME
with an inline function (only in debug mode) in order to get a
compiler warning
Paul,
imho, the root cause is a missing ampersand.
I will double check this from tomorrow only
Cheers,
Gilles
Ralph Castain wrote:
>Arg - that raises an interesting point. This is a pointer to a 64-bit number.
>Will uintptr_t resolve that problem on such platforms?
>
>
>On Aug 2, 2014, at 8:
Whether just adding a (uintptr_t) cast is sufficient or not depends on the
usage, and I don't pretend to have looked much deeper than seeing that this
macro is common to the line numbers in the warnings I quoted.
If the intent is to uniformly store a pointer then a (uintptr_t *) cast may
be approp
Arg - that raises an interesting point. This is a pointer to a 64-bit number.
Will uintptr_t resolve that problem on such platforms?
On Aug 2, 2014, at 8:12 PM, Paul Hargrove wrote:
> Looks like on a 32-bit platform a (uintptr_t) cast is desired in the
> OMPI_CAST_RTE_NAME() macro.
>
> Warnin
Looks like on a 32-bit platform a (uintptr_t) cast is desired in the
OMPI_CAST_RTE_NAME() macro.
Warnings from current trunk tarball attributable to the missing case
include:
/home/pcp1/phargrov/OMPI/openmpi-trunk-linux-x86-gcc/openmpi-1.9a1r32406/ompi/runtime/ompi_mpi_abort.c:89:
warning: cast t
