# ParaView segmentation fault when reading GMSH files (GmshIO Plugin)

**URL:** https://discourse.paraview.org/t/paraview-segmentation-fault-when-reading-gmsh-files-gmshio-plugin/8550
**Category:** Development
**Created:** [December 2, 2021, 10:45pm UTC](https://discourse.paraview.org/t/paraview-segmentation-fault-when-reading-gmsh-files-gmshio-plugin/8550 "2021-12-02T22:45:06Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![gnikit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/gnikit/32/6443_2.png) [@gnikit](https://discourse.paraview.org/u/gnikit)
#### Post date: [December 2, 2021, 10:45pm UTC](https://discourse.paraview.org/t/paraview-segmentation-fault-when-reading-gmsh-files-gmshio-plugin/8550/1 "2021-12-02T22:45:06Z")

</div>

When attempting to load a GMSH file with the GmshIO plugin that is included in ParaView 5.10.0-RC1+.  
ParaView suddenly aborts and throws an error about `libc`. I suspect that this is a bug related to different versions of `libc`.  
Can someone verify that this is not just happening to me?

## Additional info

OS: Linux (Ubuntu 20.04)  
Paraview affected versions: 5.10.0-RC1+  
GMSH version: tested against 4.0.1 and 4.8.4 (problem is probably present for all 4+ versions)  
Error:

```log
Loguru caught a signal: SIGSEGV
Stack trace:
0 0x7f90e5102210 /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f90e5102210]
( 45.741s) [paraview] :0 FATL| Signal: SIGSEGV

```

## Test files

Some simple ASCII and binary format v4 GMSH files  
[test-ascii.msh](https://discourse.paraview.org/uploads/short-url/vap5OzLphu2DYJjJgILw1ICRQLT.msh) (23.5 KB)  
[test-bin.msh](https://discourse.paraview.org/uploads/short-url/bYwmTFcQpCAYBobqTSAUGROsbbQ.msh) (32.8 KB)

## Steps to recreate

1. Launch ParaView
2. Load GmshIO Plugin, **Tools\> Manage Plugins\> GmshIO** and press Load Selected
3. Open one of the supplied test files, ParaView should segfault

---

<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: [December 3, 2021, 9:55am UTC](https://discourse.paraview.org/t/paraview-segmentation-fault-when-reading-gmsh-files-gmshio-plugin/8550/2 "2021-12-03T09:55:27Z")

</div>

I reproduce, FYI @timothee.chabat @Charles_Gueunet

---

<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: [December 3, 2021, 9:55am UTC](https://discourse.paraview.org/t/paraview-segmentation-fault-when-reading-gmsh-files-gmshio-plugin/8550/3 "2021-12-03T09:55:52Z")

</div>

@gnikit build paraview and the plugin yourself should work around it.

---

<div class="post-metadata">

### Author: ![Charles\_Gueunet](https://discourse.paraview.org/user_avatar/discourse.paraview.org/charles_gueunet/32/40_2.png) [@Charles\_Gueunet](https://discourse.paraview.org/u/Charles_Gueunet)
#### Post date: [December 3, 2021, 10:01am UTC](https://discourse.paraview.org/t/paraview-segmentation-fault-when-reading-gmsh-files-gmshio-plugin/8550/4 "2021-12-03T10:01:22Z")

</div>

This is a known issue impacting our ParaView binary, generated by the superbuild.  
There is an issue here about it: [https://gitlab.kitware.com/paraview/paraview-superbuild/-/issues/206](https://gitlab.kitware.com/paraview/paraview-superbuild/-/issues/206)

As told by @mwestphal , this can be solved by compiling ParaView yourself with `PARAVIEW_PLUGIN_ENABLE_GmshIO` set to **ON**