# fail to execute the Initialize for the vtkCPProcessor
**URL:** https://discourse.paraview.org/t/fail-to-execute-the-initialize-for-the-vtkcpprocessor/4656
**Category:** In Situ Support
**Created:** [June 23, 2020, 3:37pm UTC](https://discourse.paraview.org/t/fail-to-execute-the-initialize-for-the-vtkcpprocessor/4656 "2020-06-23T15:37:45Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@zhe](https://discourse.paraview.org/u/zhe)
#### Post date: [June 23, 2020, 3:37pm UTC](https://discourse.paraview.org/t/fail-to-execute-the-initialize-for-the-vtkcpprocessor/4656/1 "2020-06-23T15:37:45Z")
Hello,
there it following code in my program:
```
vtkCPProcessor *Processor = NULL;
...
if (Processor == NULL)
{
Processor = vtkCPProcessor::New();
Processor->Initialize();
}
```
but I got following errors when I execute the Initialize function
```
[nid00952:54524] ***Process received signal***
[nid00952:54524] Signal: Segmentation fault (11)
[nid00952:54524] Signal code: Address not mapped (1)
[nid00952:54524] Failing at address: 0x440000e8
[nid00952:54518] ***Process received signal***
[nid00952:54518] Signal: Segmentation fault (11)
[nid00952:54518] Signal code: Address not mapped (1)
[nid00952:54518] Failing at address: 0x440000e8
[nid00952:54518] [0] /lib64/libpthread.so.0(+0x132d0)[0x2aaaae5732d0]
[nid00952:54518] [1] /global/common/software/m3169/cori/openmpi/4.0.2/gnu/lib/libmpi.so.40(PMPI_Comm_set_errhandler+0x43)[0x2aaaabdc4963]
[nid00952:54518] [2] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkParallelMPI-pv5.7.so.1(_ZN18vtkMPICommunicator20GetWorldCommunicatorEv+0x3e)[0x2aaaab8a3858]
[nid00952:54524] [0] /lib64/libpthread.so.0(+0x132d0)[0x2aaaae5732d0]
[nid00952:54518] [3] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkParallelMPI-pv5.7.so.1(_ZN16vtkMPIController10InitializeEPiPPPci+0x154)[0x2aaaab8aa99c]
[nid00952:54524] [1] /global/common/software/m3169/cori/openmpi/4.0.2/gnu/lib/libmpi.so.40(PMPI_Comm_set_errhandler+0x43)[0x2aaaabdc4963]
[nid00952:54524] [2] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkParallelMPI-pv5.7.so.1(_ZN18vtkMPICommunicator20GetWorldCommunicatorEv+0x3e)[0x2aaaab8a3858]
[nid00952:54524] [3] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkParallelMPI-pv5.7.so.1(_ZN16vtkMPIController10InitializeEPiPPPci+0x154)[0x2aaaab8aa99c]
[nid00952:54518] [4] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVClientServerCoreCore-pv5.7.so.1(_ZN16vtkProcessModule10InitializeENS_12ProcessTypesERiRPPc+0x254)[0x2aaab104ca32]
[nid00952:54524] [4] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVClientServerCoreCore-pv5.7.so.1(_ZN16vtkProcessModule10InitializeENS_12ProcessTypesERiRPPc+0x254)[0x2aaab104ca32]
[nid00952:54518] [5] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVServerManagerApplication-pv5.7.so.1(_ZN23vtkInitializationHelper10InitializeEiPPciP12vtkPVOptions+0x1af)[0x2aaaaf2f5377]
[nid00952:54518] [6] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVCatalyst-pv5.7.so.1(_ZN14vtkCPCxxHelper3NewEv+0x168)[0x2aaaab0ff486]
[nid00952:54518] [7] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVCatalyst-pv5.7.so.1(_ZN14vtkCPProcessor23NewInitializationHelperEv+0x11)[0x2aaaab108bed]
[nid00952:54524] [5] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVServerManagerApplication-pv5.7.so.1(_ZN23vtkInitializationHelper10InitializeEiPPciP12vtkPVOptions+0x1af)[0x2aaaaf2f5377]
[nid00952:54524] [6] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVCatalyst-pv5.7.so.1(_ZN14vtkCPCxxHelper3NewEv+0x168)[0x2aaaab0ff486]
[nid00952:54518] [8] /global/cscratch1/sd/zw241/build_paraview/lib64/libvtkPVCatalyst-pv5.7.so.1(_ZN14vtkCPProcessor10InitializeEPKc+0x37)[0x2aaaab108c27]
...
```
My colleague reminds me the paraview might be built and linked in different mpi, I got the following results by checking the binary file that I used
```
$ ldd ./bin/Mandelbulb |grep mpi
libmpi.so.40 => /global/common/software/m3169/cori/openmpi/4.0.2/gnu/lib/libmpi.so.40 (0x00002aaaabd50000)
libmpich_gnu_82.so.3 => /opt/cray/pe/lib64/libmpich_gnu_82.so.3 (0x00002aaab5f3b000)
libopen-rte.so.40 => /global/common/software/m3169/cori/openmpi/4.0.2/gnu/lib/libopen-rte.so.40 (0x00002aaab64fd000)
libopen-pal.so.40 => /global/common/software/m3169/cori/openmpi/4.0.2/gnu/lib/libopen-pal.so.40 (0x00002aaab67b5000)
```
the mpi that I plan to use is openmpi/4.0.2, but I’m not sure why it also link to libmpich\_gnu\_82, and I’m not sure if this is issue cased the problem. It seems that the mpiexec in CMakeCache is the right one (openmpi/4.0.2)
and I also get following results when I search libmpich in the dir that I build the paraview
```
$ grep -r "libmpich" ./
Binary file ./lib64/python3.7/site-packages/mpi4py/MPI.so matches
Binary file ./lib64/libvtkIceTMPI-pv5.7.so.5.7 matches
Binary file ./lib64/libvtkIOParallelNetCDF-pv5.7.so.5.7 matches
Binary file ./lib64/libvtkFiltersParallelDIY2-pv5.7.so.5.7 matches
Binary file ./lib64/libvtkParallelMPI-pv5.7.so.5.7 matches
Binary file ./lib64/libvtkIOMPIImage-pv5.7.so.5.7 matches
Binary file ./lib64/libvtkPVClientServerCoreCore-pv5.7.so.5.7 matches
Binary file ./bin/pvtkpython matches
Binary file ./CMakeFiles/FindMPI/test_mpi_C.bin matches
```
---
### Author:  [@zhe](https://discourse.paraview.org/u/zhe)
#### Post date: [June 29, 2020, 11:24am UTC](https://discourse.paraview.org/t/fail-to-execute-the-initialize-for-the-vtkcpprocessor/4656/2 "2020-06-29T11:24:00Z")
I am not sure about the reason, but it works if I use
```auto
-DCMAKE_CXX_COMPILER=CC -DCMAKE_C_COMPILER=cc
```
to compile both Paraview and my project.