[vtkusers] bin/ProcessShader.exe coredumps on cygwin, shared libs

[Steve Robbins]

Hi,

I built VTK from CVS head (as of mid-last week) on cygwin, using  
static libs.  Subsequently, I had trouble building another project  
(http://www.ncigt.org/sign/) and decided to rebuild VTK using shared  
libs. Partway through the build, an executable named  
"bin/ProcessShader" is built and run, but on my system it is  
coredumping.

Has anyone built a recent CVS head on cygwin?  From the default  
options, I enabled shared libs, and tcl wrapping.

Here are the details of the build:

[ 53%] Generating vtkGLSLShaderLibrary.h
cd /tmp/local-build/VTK-cvs-build/Utilities/MaterialLibrary &&  
../../bin/ProcessShader.exe  
/tmp/local-build/VTK-cvs-build/Utilities/MaterialLibrary/vtkGLSLShaderLibrary.h vtkShaderGLSL Code GetCode /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestAppVarFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestVertex.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestVtkPropertyFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestMatrixFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestScalarVectorFrag.glsl  
/tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/Twisted.glsl
-- Generate module: TestAppVarFrag
/bin/sh: line 1:  1672 Aborted                 (core dumped)  
../../bin/ProcessShader.exe  
/tmp/local-build/VTK-cvs-build/Utilities/MaterialLibrary/vtkGLSLShaderLibrary.h vtkShaderGLSL Code GetCode /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestAppVarFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestVertex.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestVtkPropertyFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestMatrixFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestScalarVectorFrag.glsl  
/tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/Twisted.glsl
make[2]: *** [Utilities/MaterialLibrary/vtkGLSLShaderLibrary.h] Error 134


Actually, now that I think of it, "Error 134" probably means an ABORT  
signal (signal 6 + 128).  Possibly an uncaught exception?

I tried gdb on the executable (with same arguments):

(gdb) run
Starting program: /tmp/local-build/VTK-cvs-build/bin/ProcessShader.exe  
/tmp/local-build/VTK-cvs-build/Utilities/MaterialLibrary/vtkGLSLShaderLibrary.h vtkShaderGLSL Code GetCode /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestAppVarFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestVertex.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestVtkPropertyFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestMatrixFrag.glsl /tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/TestScalarVectorFrag.glsl  
/tmp/local-build/VTK-cvs/Utilities/MaterialLibrary/GLSLShaders/Twisted.glsl
Loaded symbols for /cygdrive/c/WINDOWS/system32/ntdll.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/kernel32.dll
Loaded symbols for /usr/bin/cygwin1.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/advapi32.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/rpcrt4.dll
Loaded symbols for /tmp/local-build/VTK-cvs-build/bin/cygvtksys.dll

Program received signal SIGSEGV, Segmentation fault.
0x00b9b7c3 in wxvault!??0Cwxvault@@QAE at XZ ()
(gdb) bt
#0  0x00b9b7c3 in wxvault!??0Cwxvault@@QAE at XZ ()
#1  0x00000000 in ?? ()


So it looks like gdb doesn't recognize the stack frame properly.  But  
if it is to be believed, the problem lies in WXVAULT.DLL.  It is  
possible, but I find that hard to believe.

So: has anyone built a recent CVS head on cygwin using shared  
libraries?  If so, what other settings did you use?

Thanks,
-Steve