Thanks Ralph. I've seen the messages generated in b...@open-mpi.org, so
I figured something was up! I was going to provide the unified diff,
but then ran into another issue in testing where we immediately ran into
a seq fault, even with this fix. It turns out that a pre-pending of
/lib64 (
Okay, I finally had time to parse this and fix it. Thanks!
On May 16, 2011, at 1:02 PM, Peter Thompson wrote:
> Hmmm? We're not removing the putenv() calls. Just adding a strdup()
> beforehand, and then calling putenv() with the string duplicated from env[j].
> Of course, if the strdup fails
Can you send your diff in unified form?
On May 11, 2011, at 4:05 PM, Peter Thompson wrote:
> We've gotten a few reports of problems with memory debugging when using
> OpenMPI under TotalView. Usually, TotalView will attach tot he processes
> started after an MPI_Init. However in the case wher
Guess I'm having trouble reading your diff...different notation than I'm used
to seeing. I'll have to parse thru it when I have more time.
On May 16, 2011, at 1:02 PM, Peter Thompson wrote:
> Hmmm? We're not removing the putenv() calls. Just adding a strdup()
> beforehand, and then calling p
Hmmm? We're not removing the putenv() calls. Just adding a strdup()
beforehand, and then calling putenv() with the string duplicated from
env[j]. Of course, if the strdup fails, then we bail out.
As for why it's suddenly a problem, I'm not quite as certain. The
problem we do show is a dou
On May 16, 2011, at 12:45 PM, Peter Thompson wrote:
> Hi Ralph,
>
> We've had a number of user complaints about this. Since it seems on the
> face of it that it is a debugger issue, it may have not made it's way back
> here. Is your objection that the patch basically aborts if it gets a bad
Hi Ralph,
We've had a number of user complaints about this. Since it seems on
the face of it that it is a debugger issue, it may have not made it's
way back here. Is your objection that the patch basically aborts if it
gets a bad value? I could understand that being a concern. Of
cours
That would be a problem, I fear. We need to push those envars into the
environment.
Is there some particular problem causing what you see? We have no other reports
of this issue, and orterun has had that code forever.
Sent from my iPad
On May 11, 2011, at 2:05 PM, Peter Thompson
wrote:
>
We've gotten a few reports of problems with memory debugging when using
OpenMPI under TotalView. Usually, TotalView will attach tot he
processes started after an MPI_Init. However in the case where memory
debugging is enabled, things seemed to run away or fail. My analysis
showed that we ha
