[Paraview] Fwd: Baffled by "floating point exceptions" in ParaView 3.6.1

Rick Angelini angel at arl.army.mil
Tue Aug 11 15:29:30 EDT 2009


Randall - that's consistent with what we saw in our environment as well.

Randall Hand wrote:
> I'm currently waiting for the admins to Install OpenMPI1.3, but in the 
> meantime I recompiled and linked against Mesa (rather than the nvidia 
> drivers).
>
> Tada, all works.  So there's definately some problem with NVidia 
> Drivers + OpenMPI1.2.x
> --
> Randall Hand
> Visualization Scientist
> http://www.yeraze.com
> http://www.vizworld.com
>
>
> On Tue, Aug 11, 2009 at 8:52 AM, Berk Geveci <berk.geveci at kitware.com 
> <mailto:berk.geveci at kitware.com>> wrote:
>
>     My guess is that there is a symbol conflict between something in
>     ParaView and OpenMPI 1.2.6. If switching to 1.3 does not fix the
>     problem, we'll have to resort to debugging this some other way.
>
>     -berk
>
>     On Fri, Aug 7, 2009 at 8:59 AM, Rick Angelini<angel at arl.army.mil
>     <mailto:angel at arl.army.mil>> wrote:
>     > Randall - try compiling against Openmpi-1.3 and see if you get
>     different
>     > results.    We saw issues with compiling Paraview 3.x against
>     Openmpi-1.2.6
>     > that went away when we switch to Openmpi-1.3.
>     >
>     >
>     >
>     > j s wrote:
>     >>
>     >> Looking online, that is a nasty FPE, since it is a result of an
>     integer
>     >> operation, not a floating point operation.
>     >>
>     >> This is occuring at address NULL, which should not be possible.
>     >> #8  0x0000000000000000 in ?? ()
>     >>
>     >> It looks like a function at address 0 is being called.  Do you
>     have more
>     >> of the trace, or is that the top?  If that is the top, can you
>     see if this
>     >> function is being invoked from a different thread?
>     >>
>     >> Juan
>     >>
>     >>
>     >> On Thu, Aug 6, 2009 at 3:47 PM, Randall Hand
>     <randall.hand at gmail.com <mailto:randall.hand at gmail.com>
>     >> <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>> wrote:
>     >>
>     >>    Ok, more information.
>     >>
>     >>    If I compile ParaView without Python and without MPI, it works
>     >>    beautifully.
>     >>
>     >>    Enabling MPI, however, causes the problem.. a GDB trace:
>     >>
>     >>
>     >>    (gdb) run
>     >>    Starting program:
>     /viz/work/rhand/pvezviz/install-MPI/bin/paraview
>     >>
>     >>    Program received signal SIGFPE, Arithmetic exception.
>     >>    0x00000030fea6911c in _int_free () from /lib64/tls/libc.so.6
>     >>    (gdb) bt
>     >>    #0  0x00000030fea6911c in _int_free () from /lib64/tls/libc.so.6
>     >>    #1  0x00000030fea69596 in free () from /lib64/tls/libc.so.6
>     >>    #2  0x00000030fe800a2b in ?? ()
>     >>    #3  0x0000007fbfffc8b0 in ?? ()
>     >>    #4  0x0000002a9758a11e in ?? ()
>     >>    #5  0x000000000000fd00 in ?? ()
>     >>    #6  0x000000000128502b in ?? ()
>     >>    #7  0x0000002aa267372a in ?? ()
>     >>    #8  0x0000000000000000 in ?? ()
>     >>    (gdb)
>     >>
>     >>    The MPI libraries I'm using:
>     >>
>     >>     MPI_EXTRA_LIBRARY
>     >>
>      /usr/local/ofed/mpi/gcc/openmpi-1.2.8/lib64/libmpi.so;/usr/local/ofed/mpi/gcc/openmpi-1.2.8/lib64/libopen-rte.so;/usr/local/ofed/mpi/gcc/openmpi-1.2.8/lib64/libopen-pal.so;/usr/lib64/libdl.so;/usr/lib64/libnsl.so;/usr/lib64/libutil.so;/usr/lib64/libm.so;/usr/lib64/libdl.so
>     >>     MPI_INCLUDE_PATH
>     >>  /usr/local/ofed/mpi/gcc/openmpi-1.2.8/include
>     >>     MPI_LIBRARY
>     >>  /usr/local/ofed/mpi/gcc/openmpi-1.2.8/lib64/libmpi_cxx.so
>     >>
>     >>    Anyone see anything obviously wrong?
>     >>
>     >>
>     >>    --
>     >>    Randall Hand
>     >>    Visualization Scientist
>     >>    http://www.yeraze.com
>     >>    http://www.vizworld.com
>     >>
>     >>
>     >>
>     >>    On Thu, Jul 30, 2009 at 10:49 AM, Rick Angelini
>     >>    <angel at arl.army.mil <mailto:angel at arl.army.mil>
>     <mailto:angel at arl.army.mil <mailto:angel at arl.army.mil>>> wrote:
>     >>
>     >>        Randall - we saw some execution-time failures of 3.6.1 that
>     >>        was related to an older version of the nVidia driver.     We
>     >>        didn't see floating point exceptions, though - we saw socket
>     >>        errors related to the client-server connection.  Moving to a
>     >>        newer version of the nVidia driver on the client side fixed
>     >>        the problem.     It doesn't make sense, but that's what
>     >>        happened!   8-)
>     >>
>     >>
>     >>
>     >>        j s wrote:
>     >>
>     >>            I had meant to send this to the list, instead of
>     just Randall.
>     >>
>     >>            ---------- Forwarded message ----------
>     >>            From: *j s* <j.s4403 at gmail.com
>     <mailto:j.s4403 at gmail.com> <mailto:j.s4403 at gmail.com
>     <mailto:j.s4403 at gmail.com>>
>     >>            <mailto:j.s4403 at gmail.com <mailto:j.s4403 at gmail.com>
>     <mailto:j.s4403 at gmail.com <mailto:j.s4403 at gmail.com>>>>
>     >>            Date: Thu, Jul 30, 2009 at 9:03 AM
>     >>            Subject: Re: [Paraview] Baffled by "floating point
>     >>            exceptions" in ParaView 3.6.1
>     >>            To: Randall Hand <randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>>>
>     >>
>     >>
>     >>            If you are running it in gdb, you might be able to do:
>     >>
>     >>            (gdb) handle SIGFPE nopass
>     >>            Signal        Stop      Print   Pass to program
>     Description
>     >>            SIGFPE        Yes       Yes     No            
>      Arithmetic
>     >>            exception
>     >>
>     >>            or
>     >>
>     >>            (gdb) handle SIGFPE nostop nopass
>     >>            Signal        Stop      Print   Pass to program
>     Description
>     >>            SIGFPE        No        Yes     No            
>      Arithmetic
>     >>            exception
>     >>
>     >>
>     >>
>     >>            On Thu, Jul 30, 2009 at 8:52 AM, Randall Hand
>     >>            <randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com> <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>>> wrote:
>     >>
>     >>               I was unable to compile 3.4 against these libraries,
>     >>            compilation
>     >>               would fail with errors in the Python libraries about
>     >>            "-fPIC".
>     >>
>     >>               I'll try again without MPI & Python, and get back
>     with you.
>     >>
>     >>               --
>     >>               Randall Hand
>     >>               Visualization Scientist
>     >>               http://www.yeraze.com <http://www.yeraze.com/>
>     >>               http://www.vizworld.com <http://www.vizworld.com/>
>     >>
>     >>
>     >>
>     >>               On Thu, Jul 30, 2009 at 8:47 AM, Berk Geveci
>     >>               <berk.geveci at kitware.com
>     <mailto:berk.geveci at kitware.com>
>     >>            <mailto:berk.geveci at kitware.com
>     <mailto:berk.geveci at kitware.com>>
>     >>            <mailto:berk.geveci at kitware.com
>     <mailto:berk.geveci at kitware.com>
>     >>            <mailto:berk.geveci at kitware.com
>     <mailto:berk.geveci at kitware.com>>>> wrote:
>     >>
>     >>                   Can you try compiling without Python and MPI?
>     Also,
>     >>            can you
>     >>                   try with
>     >>                   Mesa? I am guessing some system library is
>     causing this
>     >>                   problem but
>     >>                   without a stack trace, it will be trial-and-error
>     >>            to find out
>     >>                   which.
>     >>                   Also, do older versions work with the same
>     libraries?
>     >>
>     >>                   -berk
>     >>
>     >>                   On Thu, Jul 30, 2009 at 9:43 AM, Randall
>     >>                   Hand<randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>
>     >>            <mailto:randall.hand at gmail.com
>     <mailto:randall.hand at gmail.com>>>>
>     >>
>     >>                   wrote:
>     >>                   > I've compiled ParaView 3.6.1 three times so
>     far,
>     >>            and every
>     >>                   time it compiles
>     >>                   > successfully but when I attempt to run it, it
>     >>            dies with
>     >>                   "Floating point
>     >>                   > exception".
>     >>                   >
>     >>                   > I'm compiling it on a Linux system (RHEL4), and
>     >>            linking
>     >>                   against MPI (OpenMPE
>     >>                   > 1.2.8) and python (2.5.1).  I'm using cmake
>     2.6.4
>     >>            .  Is
>     >>                   there some known
>     >>                   > problem here?
>     >>                   >
>     >>                   > I compiled Paraview in "Debug" mode, but a
>     >>            backtrace doesn't
>     >>                   show anything
>     >>                   > but question marks.
>     >>                   > --
>     >>                   > Randall Hand
>     >>                   > Visualization Scientist
>     >>                   > http://www.yeraze.com <http://www.yeraze.com/>
>     >>                   > http://www.vizworld.com
>     <http://www.vizworld.com/>
>     >>                   >
>     >>                   > _______________________________________________
>     >>                   > Powered by www.kitware.com
>     <http://www.kitware.com>
>     >>            <http://www.kitware.com> <http://www.kitware.com/>
>     >>
>     >>                   >
>     >>                   > Visit other Kitware open-source projects at
>     >>                   >
>     http://www.kitware.com/opensource/opensource.html
>     >>                   >
>     >>                   > Please keep messages on-topic and check the
>     >>            ParaView Wiki at:
>     >>                   > http://paraview.org/Wiki/ParaView
>     >>                   >
>     >>                   > Follow this link to subscribe/unsubscribe:
>     >>                   >
>     http://www.paraview.org/mailman/listinfo/paraview
>     >>                   >
>     >>                   >
>     >>
>     >>
>     >>
>     >>               _______________________________________________
>     >>               Powered by www.kitware.com
>     <http://www.kitware.com> <http://www.kitware.com>
>     >>            <http://www.kitware.com/>
>     >>
>     >>
>     >>               Visit other Kitware open-source projects at
>     >>               http://www.kitware.com/opensource/opensource.html
>     >>
>     >>               Please keep messages on-topic and check the ParaView
>     >>            Wiki at:
>     >>               http://paraview.org/Wiki/ParaView
>     >>
>     >>               Follow this link to subscribe/unsubscribe:
>     >>               http://www.paraview.org/mailman/listinfo/paraview
>     >>
>     >>
>     >>
>     >>
>     >>
>      ------------------------------------------------------------------------
>     >>
>     >>            _______________________________________________
>     >>            Powered by www.kitware.com <http://www.kitware.com>
>     <http://www.kitware.com>
>     >>
>     >>            Visit other Kitware open-source projects at
>     >>            http://www.kitware.com/opensource/opensource.html
>     >>
>     >>            Please keep messages on-topic and check the ParaView
>     Wiki
>     >>            at: http://paraview.org/Wiki/ParaView
>     >>
>     >>            Follow this link to subscribe/unsubscribe:
>     >>            http://www.paraview.org/mailman/listinfo/paraview
>     >>
>     >>        _______________________________________________
>     >>        Powered by www.kitware.com <http://www.kitware.com>
>     <http://www.kitware.com>
>     >>
>     >>        Visit other Kitware open-source projects at
>     >>        http://www.kitware.com/opensource/opensource.html
>     >>
>     >>        Please keep messages on-topic and check the ParaView
>     Wiki at:
>     >>        http://paraview.org/Wiki/ParaView
>     >>
>     >>        Follow this link to subscribe/unsubscribe:
>     >>        http://www.paraview.org/mailman/listinfo/paraview
>     >>
>     >>
>     >>
>     > _______________________________________________
>     > Powered by www.kitware.com <http://www.kitware.com>
>     >
>     > Visit other Kitware open-source projects at
>     > http://www.kitware.com/opensource/opensource.html
>     >
>     > Please keep messages on-topic and check the ParaView Wiki at:
>     > http://paraview.org/Wiki/ParaView
>     >
>     > Follow this link to subscribe/unsubscribe:
>     > http://www.paraview.org/mailman/listinfo/paraview
>     >
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>
>     Follow this link to subscribe/unsubscribe:
>     http://www.paraview.org/mailman/listinfo/paraview
>
>


More information about the ParaView mailing list