[Paraview] Lam mpi + paraview

[Robert Maynard]

My first attempt at getting MPI working with paraview was by using the
default compiler and setting the MPI_INCLUDE_PATH and MPI_LIBRARY paths. The
problem I was running into was that I was getting underfined references when
linking the mpi libraries. The solution that Lam recommended was to use
their compiler to solve the library problems. If somebody could send me
their MPI_INCLUDE_PATH and MPI_LIBRARY configurations it would help me out
alot.

On 6/22/07, David E DeMarle <dave.demarle at kitware.com> wrote:
>
> That is odd.
>
> I have a feeling that lam's mpicc brings in or leaves out something
> important in the compilation and linking, especially when it compiles the
> non parallel paraview app. When compiling against MPICH for example we don't
> use MPICH's mpicc. But instead use normal cc and link in the extra
> libraries. Instead of setting the compiler directly, have you tried just
> turning on PARAVIEW_USE_MPI and then setting the MPI_INCLUDE_PATH and
> MPI_LIBRARY instead?
>
> cheers
> Dave
>
>
>
> On 6/22/07, Robert Maynard <thorin.hax at gmail.com> wrote:
> >
> > the backtrace seems really short to me, I did compile paraview with the
> > Debug flag.
> >
> > Program received signal SIGFPE, Arithmetic exception.
> > 0x03d79ac6 in ?? ()
> > (gdb) backtrace
> > #0  0x03d79ac6 in ?? ()
> > #1  0x00000000 in ?? ()
> > (gdb)
> >
> > On 6/22/07, David E DeMarle < dave.demarle at kitware.com> wrote:
> > >
> > > I was thinking of a stack dump not a system call trace. In gdb after
> > > the crash type backtrace and send that output to the list.
> > >
> > > Thanks Robert.
> > > Dave
> > >
> > > On 6/22/07, Robert Maynard <thorin.hax at gmail.com> wrote:
> > > >
> > > > Sure I have attached the strace output
> > > >
> > > >
> > > > On 6/22/07, David E DeMarle < dave.demarle at kitware.com> wrote:
> > > > >
> > > > > Can you send a stack trace for the floating point exception?
> > > > >
> > > > >
> > > > > On 6/22/07, Robert Maynard <thorin.hax at gmail.com > wrote:
> > > > > >
> > > > > > Yes i understand I have to link to the server in MPI now, but as
> > > > > > my first email stated, by I trying running the client now that I compiled
> > > > > > mpi support in, I get a runtime floating point exception before paraview
> > > > > > launches.
> > > > > >
> > > > > > On 6/22/07, David E DeMarle <dave.demarle at kitware.com > wrote:
> > > > > > >
> > > > > > > In 3.0 the paraview executable is not MPI parallel, only the
> > > > > > > server executables are.
> > > > > > > That is, you can no longer run "mpirun -np N paraview" but
> > > > > > > instead have to do something like "mpirun -np N pvserver&; paraview" and
> > > > > > > then use File->Choose Server to connect to the parallel server.
> > > > > > >
> > > > > > > cheers
> > > > > > > Dave DeMarle
> > > > > > >
> > > > > > > On 6/22/07, Robert Maynard < thorin.hax at gmail.com> wrote:
> > > > > > >
> > > > > > > > I have compiled paraview with mpi support using lam. I
> > > > > > > > changed the standard c and c++ compilers for paraview too mpicc and mpic++
> > > > > > > > so that all the
> > > > > > > > mpi references where aviable. The build was correctly
> > > > > > > > compiled, the problem comes when trying to launch the standalone version of
> > > > > > > > paraview.
> > > > > > > >
> > > > > > > > When launching /bin/paraview the error i get is "Floating
> > > > > > > > point exception", using gdb to trace the error I get
> > > > > > > >   New process 16350]
> > > > > > > >
> > > > > > > >  Program received signal SIGFPE, Arithmetic exception.
> > > > > > > >  0x05761ac6 in ?? ()
> > > > > > > >
> > > > > > > > Now if I try to run /bin/paraview with mpirun -np 1, it
> > > > > > > > tells me that paraview  did not invoke MPI_INIT before quitting. The problem
> > > > > > > > seems to only
> > > > > > > > happen with standalone version, as /bin/pvserver runs
> > > > > > > > perfectly fine with mpirun
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > ParaView mailing list
> > > > > > > > ParaView at paraview.org
> > > > > > > > http://www.paraview.org/mailman/listinfo/paraview
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > ParaView mailing list
> > > > > > ParaView at paraview.org
> > > > > > http://www.paraview.org/mailman/listinfo/paraview
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > ParaView mailing list
> > > > ParaView at paraview.org
> > > > http://www.paraview.org/mailman/listinfo/paraview
> > > >
> > > >
> > > >
> > >
> >
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20070622/4eed4dc3/attachment.htm