I have been testing some code against openmpi lately that always causes it
to crash during certain mpi function calls. The code does not seem to be
the problem, as it runs just fine against mpich. I have tested it against
openmpi 1.2.5, 1.2.6, and 1.2.7 and they all exhibit the same problem.
Also
On Oct 3, 2008, at 9:26 AM, Ralph Castain wrote:
However, what about memchecker? Per my earlier note that crossed
this one, is the current behavior a "bug"?
As I said if one request the memchecker and we cannot satisfy it, then
we should exit with a big error message that clearly state tha
Ah! I was unaware of that behavior for visibility. Thanks for
clarifying - that's a behavior I can live with.
However, what about memchecker? Per my earlier note that crossed this
one, is the current behavior a "bug"?
On Oct 3, 2008, at 7:18 AM, George Bosilca wrote:
Ralph in order to hav
Ralph in order to have the behavior you describe for the visibility
feature just don't specify --enable-visibility. This will enable it if
the feature is supported and disable (plus a small warning) if not.
We decided a while ago that 1) we should have a consistent behavior
for similar scen
On Oct 3, 2008, at 1:59 AM, Aurélien Bouteiller wrote:
Hi Ralph,
1. No. Having visibility turned off without knowing it is the best
way for us to commit bugs in the trunk without noticing, I mean
before somebody else get the leg caught in the "not-compiling-trunk
trap". I had more of my
Hi Ralph,
1. No. Having visibility turned off without knowing it is the best way
for us to commit bugs in the trunk without noticing, I mean before
somebody else get the leg caught in the "not-compiling-trunk trap". I
had more of my share of responsibility for that kind of problems in
the
