[Paraview] Paraview build failed 2.0.1 kwProcessXML
Terry Jordan
tejj at hotmail.com
Tue Apr 26 08:11:09 EDT 2005
I got it to build and everything works fine until I try to do a parallel
rendering with composite. I set the composite down to 0MB to make sure it
is doing compositing on all data sets. So it crashes with the following
errors:
# mpirun -np 6 -machinefile /root/pv.nodefile
/usr/local/paraview-2.0.1/bin/pvserver
Listen on port: 11111
Waiting for client...
connected to port 11111
Client connected.
Process id: 1 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb4d0): bad X server connection.
Process id: 1 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb4d0): bad X server connection.
p1_27744: p4_error: interrupt SIGSEGV: 11
Process id: 4 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 4 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p4_27720: p4_error: interrupt SIGSEGV: 11
Process id: 3 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 3 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p3_27132: p4_error: interrupt SIGSEGV: 11
Process id: 5 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 5 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p5_27784: p4_error: interrupt SIGSEGV: 11
Process id: 2 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 2 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p2_26745: p4_error: interrupt SIGSEGV: 11
ids1:~ # mpirun -np 6 -machinefile /root/pv.nodefile
/usr/local/paraview-2.0.1/bin/pvserver
Listen on port: 11111
Waiting for client...
connected to port 11111
Client connected.
Process id: 1 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 1 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p1_31796: p4_error: interrupt SIGSEGV: 11
Process id: 2 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 2 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p2_31004: p4_error: interrupt SIGSEGV: 11
Process id: 4 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 4 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p4_31161: p4_error: interrupt SIGSEGV: 11
Process id: 3 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 3 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p3_30222: p4_error: interrupt SIGSEGV: 11
Process id: 5 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 326
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
Process id: 5 >> ERROR: In
/scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 169
vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
p5_31433: p4_error: interrupt SIGSEGV: 11
----Original Message Follows----
From: Brad King <brad.king at kitware.com>
To: Terry Jordan <tejj at hotmail.com>
CC: paraview at paraview.org
Subject: Re: [Paraview] Paraview build failed 2.0.1 kwProcessXML
Date: Fri, 22 Apr 2005 13:49:29 -0400
Terry Jordan wrote:
>ids7:/scratch/paraview-2.0.1_src/build # ldd
>/scratch/paraview-2.0.1_src/build/bin/kwProcessXML
> libvtkCommon.so => /usr/local/vtk/lib/vtk/libvtkCommon.so
>(0x40018000)
> libkwsys.so => /usr/local/lib/libkwsys.so (0x402a3000)
>From where did this kwsys library come? ParaView only ever installs
libraries in PREFIX/lib/paraview-2.0. Perhaps you ran "make install" in an
older version of ParaView before all the proper install rules were written?
It looks like you've built both shared and static builds of ParaView in that
build tree. Once the shared libraries are present the linker will always
favor them over the static versions. My guess is you once built with shared
libraries and then switched back to static libraries. This would prevent
the RPATH from ending up in the executable because CMake thinks it is
linking in static libraries. Then the linker finds the shared library first
and adds it with no RPATH, so the dynamic linker finds one from the system
at runtime.
Did you turn on CMAKE_SKIP_RPATH in this build tree or add
/usr/local/vtk/lib/vtk to LD_LIBRARY_PATH?
I suggest you remove all traces of older VTK and ParaView versions from
/usr/local and from any environment variables. Then create a fresh build
tree for ParaView and start again.
-Brad
More information about the ParaView
mailing list