[Mesa-dev] VTK Offscreen Segfaults

tom fogal tfogal at sci.utah.edu
Wed Aug 4 13:21:12 PDT 2010


"Kevin H. Hobbs" <hobbsk at ohiou.edu> writes:
> On 08/04/2010 03:01 PM, tom fogal wrote:
> >
> > 3) Doesn't seem likely that ::OpenGLInit calls
> > vbo_exec_EvalCoord1fv :) Are you missing debug symbols in Mesa?
> > Could you get a stack trace w/ full debug symbols?
>
[snip]
> Program received signal SIGSEGV, Segmentation fault.
> vbo_exec_EvalCoord1fv (u=3D0x203) at vbo/vbo_exec_api.c:458
> 458        vbo_exec_EvalCoord1f( u[0] );
> Missing separate debuginfos, use: debuginfo-install
> expat-2.0.1-10.fc13.x86_64 fontconfig-2.8.0-1.fc13.x86_64
[snip]
> (gdb) bt
> #0  vbo_exec_EvalCoord1fv (u=3D0x203) at vbo/vbo_exec_api.c:458
> #1  0x00007ffff7b3263d in vtkOpenGLRenderWindow::OpenGLInit (this=3D0x69d=
> 310)

I am not sure what is wrong here, but something is.
vbo_exec_EvalCoord1fv and vbo_exec_EvalCoord1f are both static methods
in that file... there is no way OpenGLInit could call them.  They must
be called automagically during OSMesaCreateContext or similar, but we
should *see* the CreateContext call somewhere in the backtrace and I am
not sure why we do not.

Can you try valgrind?  Perhaps somehow the generated dispatch
code is jumping into lalaland and somehow magically ends up in
vbo_exec_EvalCoord1fv (pretty far-fetched, but I'm out of ideas
here...).

-tom

>     at /home/kevin/kitware/VTK/Rendering/vtkOpenGLRenderWindow.cxx:241
> #2  0x00007ffff7b8c45e in vtkXOpenGLRenderWindow::CreateOffScreenWindow
> (this=3D0x69d310, width=3D300, height=3D300)
>     at /home/kevin/kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:951
> #3  0x00007ffff7b8c8dd in vtkXOpenGLRenderWindow::Initialize (this=3D0x69=
> d310)
>     at /home/kevin/kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1066
> #4  0x00007ffff7b8cce3 in vtkXOpenGLRenderWindow::Start (this=3D0x69d310)=
> 
>     at /home/kevin/kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1185
> #5  0x00007ffff7a54fc1 in vtkRenderWindow::DoStereoRender (this=3D0x69d31=
> 0)
>     at /home/kevin/kitware/VTK/Rendering/vtkRenderWindow.cxx:687
> #6  0x00007ffff7a54f92 in vtkRenderWindow::DoFDRender (this=3D0x69d310)
>     at /home/kevin/kitware/VTK/Rendering/vtkRenderWindow.cxx:676
> #7  0x00007ffff7a54992 in vtkRenderWindow::DoAARender (this=3D0x69d310)
>     at /home/kevin/kitware/VTK/Rendering/vtkRenderWindow.cxx:563
> #8  0x00007ffff7a53da2 in vtkRenderWindow::Render (this=3D0x69d310)
>     at /home/kevin/kitware/VTK/Rendering/vtkRenderWindow.cxx:376
> #9  0x00007ffff7b8f743 in vtkXOpenGLRenderWindow::Render (this=3D0x69d310=
> )
>     at /home/kevin/kitware/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1845
> #10 0x0000000000432696 in TestOSConeCxx (argc=3D7, argv=3D0x7fffffffd960)=
> 
>     at /home/kevin/kitware/VTK/Rendering/Testing/Cxx/TestOSConeCxx.cxx:68=
> 
> #11 0x000000000041b683 in main (ac=3D7, av=3D0x7fffffffd960)
>     at
> /home/kevin/kitware/VTK_Build/Rendering/Testing/Cxx/RenderingCxxTests.cxx=
> :454


More information about the mesa-dev mailing list