Hi,<br><br>gmsh is giving the following error:<br> <br> $ gmsh tmp.geo -3 -nopopup -part 2 -format msh -o tmp.msh<br> Info : Running 'gmsh tmp.geo -3 -nopopup -part 2 -format msh -o tmp.msh' [1 <br> node(s), max. 2 thread(s)]<br>
...<br> Info : 84 vertices 198 elements<br> Info : Building graph...<br> Info : Partitioning graph...<br> *** glibc detected *** gmsh: free(): invalid next size (fast): 0x000000000225f000 ***<br> ======= Backtrace: =========<br>
/lib/x86_64-linux-gnu/libc.so.6(+0x78a96)[0x7f0b17474a96]<br> /lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f0b17478d7c]<br> gmsh(_Z7fillit_IN9__gnu_cxx17__normal_iteratorIPP11MHexahedronSt6vectorIS3_SaIS3_EEEEEvRSt8multimapI5MFaceP8MElement9Less_FaceSaISt4pairIKSA_SC_EEET_SK_+0x265) <br>
[0x7c2a35]<br> ...<br> 7f0b17794000-7f0b17795000 rw-p 00198000 08:01 3674265 /lib/x86_64-<br> linux-gnu/libc-2.13.soAborted<br> <br>when using the following geo file:<br><br> ny = 1;<br>
nx = 20;<br> nz = 1;<br> cellSize = 1 - 0.005;<br> height = 1;<br> width = 20;<br> depth = 1;<br><br> Point(1) = {0, 0, 0, cellSize};<br>
Point(2) = {width, 0, 0, cellSize};<br> Line(3) = {1, 2};<br> out[] = Extrude{0, height, 0} {<br> Line{3}; Layers{ ny }; Recombine;<br> };<br> Extrude{0, 0, depth} {<br>
Surface{ out[1] }; Layers{ nz }; Recombine;<br> }<br><br>This geo file works fine with only one partition. The system is<br><br> $ uname -a<br> Linux Sandbox 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 <br>
x86_64 x86_64 x86_64 GNU/Linux<br><br>I'm using the system gmsh (the one you get with apt-get on Ubuntu)<br><br> $ gmsh --version<br> 2.5.1<br> $ which gmsh<br> /usr/bin/gmsh<br><br>An older "hand built" gmsh in /usr/local/bin works fine for this problem<br>
<br> $ /usr/local/bin/gmsh --version<br> 2.5.0<br> $ /usr/local/bin/gmsh tmp.geo -3 -nopopup -part 2 -format msh -o tmp.msh<br> Info : Running '/usr/local/bin/gmsh-bkup tmp.geo -3 -nopopup -part 2 -format msh <br>
-o tmp.msh' [1 node(s), max. 1 thread(s)]<br> ...<br> Info : Stopped on Wed Dec 14 11:47:02 2011<br><br>Could this be a 64 versus 32 bit library issue with the system install or something like that?<br> <br>Thanks<br>
<br>-- <br>Daniel Wheeler<br>