ittle self-serving ;-)
Cheers,
Peter Thompson
Ralph Castain wrote:
Ick - appears that got dropped a long time ago. I'll add it back in and post a
CMR for 1.4 and 1.5 series.
Thanks!
Ralph
On Mar 21, 2011, at 11:08 AM, David Turner wrote:
Hi,
About a month ago, this topic was di
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
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
ote:
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 get
n 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, then we bail out.
As for why it's suddenly a pro
I wonder if someone might have possible ideas to explore as to why this
program might not be working correctly under TotalView. Essentially a
user is running a very simple hello world like program that does this:
#include
#include
#include
int main(int argc, char **argv)
{
MPI_Init( &argc
r is this a bug (that might not affect anyone
other than TotalView memory debug users?)
Thanks,
Peter Thompson
Gutierrez
Los Alamos National Laboratory
On Oct 1, 2009, at 11:25 AM, Peter Thompson wrote:
> We had a question from a user who had turned on memory debugging in
> TotalView and experience a memory event error Invalid memory
> alignment request. Having a 1.3.3 build of OpenMPI handy
The value of 4 might be invalid (though maybe on a 32b machine, it would be
okay?) but it's enough to allow TotalView to continue on without raising a
memory event, so I'm okay with it ;-)
PeterT
Ashley Pittman wrote:
Simple malloc() returns pointers that are at least eight byte aligned
anywa
I've tried a few builds of 1.4 on Snow Leopard, and trying to start up TotalView
gets some of the more 'standard' problems. Either the typdef for MPIR_PROCDESC
can't be found, or MPIR_PROCTABLE is missing. You can get things to work if you
start up TotalView first and then pick your program an
Hi Jeff,
Sorry, speaking in shorthand again.
Jeff Squyres wrote:
On Jan 8, 2010, at 5:03 PM, Peter Thompson wrote:
I've tried a few builds of 1.4 on Snow Leopard, and trying to start up TotalView
gets some of the more 'standard' problems.
I don't quite know what y
might be apparent in the spec file, but it's
certainly not apparent to me! Any help or advice would be appreciated.
Cheers,
Peter Thompson
http://lists.rpm.org/pipermail/rpm-list/2009-January/000122.html
%define debug_package %{nil}
%define __strip /bin/true
Ashley.
On 25 May 2010, at 00:25, Peter Thompson wrote:
I have a user who prefers building rpm's from the srpm. That's okay, but for
debugging via TotalView it cr
the executables and shared libraries, and we would then
be able to debug with Open MPI without a problem. I'm not sure if this
is the best place to offer that suggestion, but I imagine it's not a bad
place to start. ;-)
Regards,
Peter Thompson
14 matches
Mail list logo
