[vtk-developers] Problem in vtkXOpenGLTextMapper.

[Prabhu Ramachandran]

hi,

Last night I wrote about a segfault problem and attached a simple
Python app that demonstrates the problem.  Here is more information.

I rebuilt everything with -O2 -g and retried.  Unfortunately the
machine where I compiled it has the nVidia openGL libraries and the
debugger doesnt get any further than what I had already posted.  I
moved the VTK libs to a Mesa based libarary and tried with the same
example that I emailed.  Here is the resulting backtrace.


#0  0x41baf686 in gl_error () from /usr/lib/libGL.so.1
#1  0x41cfc394 in gl_reduce_prim () from /usr/lib/libGL.so.1
#2  0x41e2bf99 in vtkXOpenGLTextMapper::RenderGeometry ()
   from /tmp/vtk/lib/libvtkRendering.so
#3  0x41e2c3dd in vtkXOpenGLTextMapper::RenderOpaqueGeometry ()
   from /tmp/vtk/lib/libvtkRendering.so
#4  0x407527cc in vtkActor2D::RenderOpaqueGeometry ()
   from /tmp/vtk/lib/libvtkCommon.so
#5  0x41dd9dad in vtkScalarBarActor::RenderOpaqueGeometry ()
   from /tmp/vtk/lib/libvtkRendering.so
#6  0x41dd27c3 in vtkRenderer::UpdateGeometry ()
   from /tmp/vtk/lib/libvtkRendering.so
#7  0x41e1f258 in vtkOpenGLRenderer::DeviceRender ()
   from /tmp/vtk/lib/libvtkRendering.so
#8  0x41dd1c7b in vtkRenderer::Render () from /tmp/vtk/lib/libvtkRendering.so
#9  0x41dd691a in vtkRendererCollection::Render ()
   from /tmp/vtk/lib/libvtkRendering.so
#10 0x41dd0139 in vtkRenderWindow::DoStereoRender ()
   from /tmp/vtk/lib/libvtkRendering.so
#11 0x41dce90a in vtkRenderWindow::DoFDRender ()
   from /tmp/vtk/lib/libvtkRendering.so
#12 0x41dce576 in vtkRenderWindow::DoAARender ()
   from /tmp/vtk/lib/libvtkRendering.so
#13 0x41dcde34 in vtkRenderWindow::Render ()
   from /tmp/vtk/lib/libvtkRendering.so
#14 0x41e2aec1 in vtkXOpenGLRenderWindow::Render ()
   from /tmp/vtk/lib/libvtkRendering.so
#15 0x41a027ff in PyvtkXOpenGLRenderWindow_Render ()
   from /tmp/vtk/lib/libvtkRenderingPython.so

Is this informaiton enough?  Or do you want me to write a c++
application and manually run through the debugger and catch the bug
*exactly* where it happens??  This would not be that easy for me to do
right now since I am pretty hard pressed for time.  But if necessary I
can do it when I get the chance.

Thanks,

prabhu