Looks like this should be fixed in my PR #101 - could you please review it?
Thanks
Ralph
> On Nov 26, 2014, at 8:14 PM, Ralph Castain wrote:
>
> Aha - I see what happened. I have that param set to false in my default mca
> param file. If I set it to true on the cmd line,
Aha - I see what happened. I have that param set to false in my default mca
param file. If I set it to true on the cmd line, then I run without segfaulting.
Thanks!
Ralph
> On Nov 26, 2014, at 5:55 PM, Gilles Gouaillardet
> wrote:
>
> Ralph,
>
> let me
Ralph,
let me correct and enhance my previous statement :
- i cannot reproduce your crash in my environment (RHEL6 like vs your
RHEL7 like)
(i configured with --enable-debug --enable-picky)
- i can reproduce the crash with
mpirun --mca mpi_param_check false
- if you configured with
> On Nov 26, 2014, at 5:06 PM, Gilles Gouaillardet
> wrote:
>
> I will double check this(afk right now)
> Are you running on a rhel6 like distro with gcc ?
Yeah, I’m running CentOS7 and gcc 4.8.2
>
> Iirc, crash vs mpi error is ruled by --with-param-check or
I will double check this(afk right now)
Are you running on a rhel6 like distro with gcc ?
Iirc, crash vs mpi error is ruled by --with-param-check or something like
this...
Cheers,
Gilles
Ralph Castain さんのメール:
>I tried it with both the fortran and c versions - got the same
I tried it with both the fortran and c versions - got the same result.
This was indeed with a debug build. I wouldn’t expect a segfault even with an
optimized build, though - I would expect an MPI error, yes?
> On Nov 26, 2014, at 4:26 PM, Gilles Gouaillardet
>
I will have a look
Btw, i was running the fortran version, not the c one.
Did you confgure with --enable--debug ?
The program sends to a rank *not* in the communicator, so this behavior could
make some sense on an optimized build.
Cheers,
Gilles
Ralph Castain さんのメール:
>Ick -