[mpich-discuss] about installation

[Jain, Rohit]

Hi Anthony,

I am currently using mpd, but after upgrading to 1.4, I plan to use hydra.

Do I need to use --enable-debuginfo, even if I don't want to debug 'inside' MPICH2?
I haven't been using this option so far with our configuration, and we can debug our application with totalview. Has that changed with 1.4?

Regards,
Rohit


-----Original Message-----
From: mpich-discuss-bounces at mcs.anl.gov [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Anthony Chan
Sent: Tuesday, June 28, 2011 9:31 AM
To: mpich-discuss at mcs.anl.gov
Subject: Re: [mpich-discuss] about installation


Are you using mpd ?  If not, --enable-totalview isn't going to
do anything for you (I just searched all configure.in in 1.4.x
branch and only mpd's configure.in supports --enable-totalview).
I think you need to use --enable-debuginfo for debugger support
in recent mpich2 releases, like 1.4.

A.Chan

----- Original Message -----
> Thanks Dave.
> 
> I am attaching totalview to mpiexec directly:
> totalview python -a `which mpiexec` -tvsu a.exec
> Can someone confirm what enable-totalview does and when it is needed?
> 
> 
> > --enable-totalview: If I just want to run totalview with my
> > application and debug application's code, not inside MPICH code, Do
> > I need to use this option?
> 
> I'm not 100% sure what this option does. I _think_ that it causes
> additional helper code and shared libraries to be built with that
> allow Totalview to locate processes within an MPI job and inspect the
> message queues. Specifying this option may also require you to build
> with shared libraries, but someone else might need to confirm that.
> 
> If you just want to attach to individual processes manually with
> Totalview, you may not need this option.
> 
> Regards,
> Rohit
> 
> 
> -----Original Message-----
> From: mpich-discuss-bounces at mcs.anl.gov
> [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Dave Goodell
> Sent: Monday, June 27, 2011 3:29 PM
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [mpich-discuss] about installation
> 
> On Jun 27, 2011, at 5:03 PM CDT, Jain, Rohit wrote:
> 
> > Hi Dave,
> >
> > I am configuring new installation, and looking at my current config
> > options, and need some clarification.
> >
> > --enable-shared: If I just want to run machine installed valgrind on
> > my application, and trying to find issues back in MPICH code, do I
> > need to use this option?
> 
> If you want to use the valgrind MPI wrappers, you will need to pass
> "--enable-shared". However, you will probably also need to rebuild
> your valgrind copy after building MPICH2 then. The valgrind MPI
> wrappers are only for debugging problems *above* MPICH2, so if you
> want to debug within MPICH2 then you do not need to enable shared
> libraries.
> 
> If you want to debug MPICH2 itself with valgrind then I recommend
> "--enable-g=meminit,dbg" at a minimum, and you may also want to add
> "mem" to that list:
> http://wiki.mcs.anl.gov/mpich2/index.php/Support_for_Debugging_Memory_Allocation
> 
> 
> -Dave
> 
> > Regards,
> > Rohit
> >
> 
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
_______________________________________________
mpich-discuss mailing list
mpich-discuss at mcs.anl.gov
https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss