# Floating point exception when trying to run ./paraview in linux

**URL:** https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353
**Category:** ParaView Support
**Created:** [April 4, 2022, 6:01pm UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353 "2022-04-04T18:01:42Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![foghorn](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/b5a626/32.png) [@foghorn](https://discourse.paraview.org/u/foghorn)
#### Post date: [April 4, 2022, 6:01pm UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353/1 "2022-04-04T18:01:42Z")

</div>

When I try to start paraview version 5.10.1-MPI in chrome os linux, it immediately fails with this error.

```auto
./paraview
error: exception occurred: Floating-point exception

```

I installed dependencies with this command:

```auto
sudo apt-get install git cmake build-essential libgl1-mesa-dev libxt-dev qt5-default libqt5x11extras5-dev libqt5help5 qttools5-dev qtxmlpatterns5-dev-tools libqt5svg5-dev python3-dev python3-numpy libopenmpi-dev libtbb-dev ninja-build

```

I had to remove qt5-default in the above command for it to work. Supposedly a workaround is to use:

```auto
sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools

```

---

<div class="post-metadata">

### Author: ![foghorn](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/b5a626/32.png) [@foghorn](https://discourse.paraview.org/u/foghorn)
#### Post date: [April 5, 2022, 5:50am UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353/2 "2022-04-05T05:50:48Z")

</div>

I think the problem is with mpiexec. When I compile paraview from source, it shows much more debug info.

```auto
penguin:32715] ***Process received signal***
[penguin:32715] Signal: Floating point exception (8)
[penguin:32715] Signal code: Integer divide-by-zero (1)
[penguin:32715] Failing at address: 0x7f03d5dbd06b
[penguin:32715] [0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14140)[0x7f03d607e140]
[penguin:32715] [1] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x4206b)[0x7f03d5dbd06b]
[penguin:32715] [2] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x42f67)[0x7f03d5dbdf67]
[penguin:32715] [3] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x4378b)[0x7f03d5dbe78b]
[penguin:32715] [4] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x830e)[0x7f03d5d8330e]
[penguin:32715] [5] /lib/x86_64-linux-gnu/libhwloc.so.15(hwloc_topology_load+0x4a7)[0x7f03d5d8b557]
[penguin:32715] [6] /lib/x86_64-linux-gnu/libopen-pal.so.40(opal_hwloc_base_get_topology+0x1194)[0x7f03d5e6c4f4]
[penguin:32715] [7] /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_ess_hnp.so(+0x5146)[0x7f03d5b70146]
[penguin:32715] [8] /lib/x86_64-linux-gnu/libopen-rte.so.40(orte_init+0x29c)[0x7f03d611864c]
[penguin:32715] [9] /lib/x86_64-linux-gnu/libopen-rte.so.40(orte_daemon+0x22d)[0x7f03d60c502d]
[penguin:32715] [10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f03d5ecbd0a]
[penguin:32715] [11] orted(+0x115a)[0x56f41c94a15a]
[penguin:32715] ***End of error message***
[penguin:32712] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 716
[penguin:32712] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172

```

(continues)

When I run mpiexec:

```auto
[penguin:32745] ***Process received signal***
[penguin:32745] Signal: Floating point exception (8)
[penguin:32745] Signal code: Integer divide-by-zero (1)
[penguin:32745] Failing at address: 0x7e36eca5a06b
[penguin:32745] [0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd60)[0x7e36ecac9d60]
[penguin:32745] [1] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x4206b)[0x7e36eca5a06b]
[penguin:32745] [2] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x42f67)[0x7e36eca5af67]
[penguin:32745] [3] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x4378b)[0x7e36eca5b78b]
[penguin:32745] [4] /lib/x86_64-linux-gnu/libhwloc.so.15(+0x830e)[0x7e36eca2030e]
[penguin:32745] [5] /lib/x86_64-linux-gnu/libhwloc.so.15(hwloc_topology_load+0x4a7)[0x7e36eca28557]
[penguin:32745] [6] /lib/x86_64-linux-gnu/libopen-pal.so.40(opal_hwloc_base_get_topology+0x1194)[0x7e36ecd084f4]
[penguin:32745] [7] /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_ess_hnp.so(+0x5146)[0x7e36ec84f146]
[penguin:32745] [8] /lib/x86_64-linux-gnu/libopen-rte.so.40(orte_init+0x29c)[0x7e36ecdcd64c]
[penguin:32745] [9] /lib/x86_64-linux-gnu/libopen-rte.so.40(orte_submit_init+0x91d)[0x7e36ecdd1dcd]
[penguin:32745] [10] mpiexec(+0x12bf)[0x564d685ba2bf]
[penguin:32745] [11] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7e36ecab4d0a]
[penguin:32745] [12] mpiexec(+0x113a)[0x564d685ba13a]
[penguin:32745] ***End of error message***
Floating point exception (core dumped)

```

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 5, 2022, 8:44am UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353/3 "2022-04-05T08:44:50Z")

</div>

Hi @foghorn ,

How do you install ParaView ?

Are you using a ARM or x86 device ?

Best,

---

<div class="post-metadata">

### Author: ![foghorn](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/b5a626/32.png) [@foghorn](https://discourse.paraview.org/u/foghorn)
#### Post date: [April 5, 2022, 3:02pm UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353/4 "2022-04-05T15:02:27Z")

</div>

I unzipped the tarball for 5.10.1-MPI, ran the apt-get install commands in the 1st post (with “qt5-default” removed from the first command), and then ran ./paraview .

I also built it from source using the instructions at:  
[https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md](https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md)  
This showed debug messages but also failed.

Finally, I built 5.10.1-MPI from source with the MPI option turned OFF. This runs successfully.

So, it is definitely a problem with MPI on my system. I want to continue to try to get the MPI version of paraview working.

My device architecture is x86\_64.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [April 5, 2022, 4:35pm UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353/5 "2022-04-05T16:35:46Z")

</div>

foghorn,  
I would suggest that you NOT use the MPI version. MPI builds have been shown to be problematic for me with builtiin server (i.e., not connected to a remote server). I always give my users the non MPI version. ParaView is becoming threaded, which negates the need for MPI.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [April 5, 2022, 4:37pm UTC](https://discourse.paraview.org/t/floating-point-exception-when-trying-to-run-paraview-in-linux/9353/6 "2022-04-05T16:37:39Z")

</div>

Hmmm … I just looked, and they are all MPI enabled. I will poke the developers and see what they say.
