Thanks for your prompt reply!
Yes, I am using version 4.11 that I downloaded few days ago.
More precisely, I downloaded the PETSc version, already in binary format, for Windows.
I tried with:
mpiexec.exe -np 2 FreeFem+±mpi.exe meshtest5.edp
FreeFem+±mpi.exe meshtest5.edp
from both PowerShell and Command Prompt. Same answer:
Number of triangle(s) = 14169
Mesh area = 60978.2
Border length = 12548.4
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range […]
BUT I ALSO DISCOVERED THAT I HAVE THE SAME PROBLEM ON ANY 3D MESH.
HERE A VERY SIMPLE EXAMPLE:
This FAILS with seg fault, creating a file “meshCubeDiff.mesh” with size equal to zero:
load “PETSc” // PETSc plugin
macro dimension()3// EOM // 2D or 3D
include “macro_ddm.idp” // additional DDM functions
int[int] LL = [1,2, 1,2, 1,1];
mesh3 Tht = cube(10,10,10, [x, y, z], label = LL); // global mesh
savemesh(Tht,“meshCubeDiff.mesh”);
However THIS WORKS LIKE A CHARM (PERFECTLY), creating two mesh files:
load “PETSc” // PETSc plugin
macro dimension()2// EOM // 2D or 3D
include “macro_ddm.idp” // additional DDM functions
mesh Th2D = square(50, 10, [5 * x, y]);
savemesh(Th2D,“meshSquareDiff.mesh”);
THE ONLY DIFFERENCE I SEE IS THAT THE FIRST IS A 3D MESH WHILE THE SECOND IS A 2D MESH.
Square.edp (313 Bytes)
Cube.edp (364 Bytes)
These are very simple examples.
Do you see the same results?
Thanks again
Best regards
Riccardo