[petsc-users] possible development on Windows?

[Satish Balay]

Just one note wrt debugging with MS compilers.

I think the following also works with MPICH

mpiexec -localonly -n 2 msdev [or equivalent new name?] ex1.exe

Satish

On Sun, 6 Nov 2011, Dominik Szczerba wrote:

> Hi Alexander,
> 
> Are you running Windows HPC edition? According to google, it is
> required for the referred MPI Cluster Debugger.
> 
> I would also appreciate some more hints on "and something else", if
> you have them.
> 
> Many thanks,
> Dominik
> 
> On Sun, Nov 6, 2011 at 3:55 PM, Alexander Grayver
> <agrayver at gfz-potsdam.de> wrote:
> > Hi,
> >
> > I work with Petsc both under Linux and Windows.
> > I develop in Fortran and it makes things even more tricky sometimes. My
> > compilers are those included in VS 2008 and IFC 12 + MKL's BLAS/LAPACK for
> > Fortran (however I started to work with petsc using IFC 10.1 and downloaded
> > BLAS/LAPACK using petsc configure options).
> > The most tricky part for me was to build petsc properly, although all
> > problems are directly and indirectly related to the Fortran usage. So if you
> > write in C/C++ I would say it's going to be easy for you. Anyway I can share
> > my configuration line if you get some problems.
> > I use VS IDE and debug applications in it. For sequential programs it is no
> > problems, for MPI you have to install some additional tools (MPI Cluster
> > Debugger and something else) and just switch debugger type from VS whenever
> > you want. To make this debugger working with IFC cost me a couple of days
> > and a lot of googling, but again for C/C++ it should be easy.
> > Unfortunately, there are no things like valgrind for Windows. I couldn't
> > find at least.
> >
> > Regards,
> > Alexander
> >
> > On 06.11.2011 11:43, Dominik Szczerba wrote:
> >>
> >> I am normally working and developing my codes on linux, only compiling
> >> them at the end for Windows, but need to evaluate the possibilities to
> >> also efficiently develop on Windows. Is anyone developing Petsc based
> >> applications on Windows and could share some experiences? In
> >> particular, is it possible to debug only on Cygwin's gdb port or also
> >> to use (somehow) the Visual Studio's built in debugger? Are there
> >> tools comparable to valgrind to detect MPI-aware illegal memory
> >> accesses and leaks? I heard about TotalView, but never worked with it.
> >>
> >> Thanks for any thoughts,
> >> Dominik
> >
> >
>