[vtk-developers] LONG backtrace of segfault in Geovis-TestCoincidentGeoGraphRepresentation2D on bubbles OSMesa build
David Cole
david.cole at kitware.com
Tue Nov 2 12:28:13 EDT 2010
Why are we doing this? (line 328 and surroundings of Views/vtkRenderView.cxx)
if (caller == this->GetInteractor() && eventId == vtkCommand::RenderEvent)
{
vtkDebugMacro(<< "interactor causing a render event.");
this->Render();
}
We should not call Render in repsonse to a RenderEvent unless we are
100% confident that calling Render will not throw another RenderEvent.
I think this is one of the definitions of an infinite loop. Am I
missing something?
On Tue, Nov 2, 2010 at 12:01 PM, Kevin H. Hobbs <hobbsk at ohiou.edu> wrote:
> On 11/01/2010 05:02 PM, Aashish Chaudhary wrote:
>> quickly looking this looks not familiar. I will have a look.
>>
>
> The outer 20 levels of the backtrace are :
>
> bt -20
> #130977 0x00007ffff697da74 in vtkRenderView::Render (this=0x641f20) at
> /home/kevin/kitware/VTK/Views/vtkRenderView.cxx:305
> #130978 0x00007ffff7dd632b in vtkGeoView2D::Render (this=0x641f20) at
> /home/kevin/kitware/VTK/Geovis/vtkGeoView2D.cxx:116
> #130979 0x00007ffff697dcf8 in vtkRenderView::ProcessEvents
> (this=0x641f20, caller=0x6429a0, eventId=5, callData=0x0) at
> /home/kevin/kitware/VTK/Views/vtkRenderView.cxx:328
> #130980 0x00007ffff6985615 in vtkView::Command::Execute (this=0x641e20,
> caller=0x6429a0, eventId=5, callData=0x0) at
> /home/kevin/kitware/VTK/Views/vtkView.cxx:52
> #130981 0x00007ffff36291f5 in vtkSubjectHelper::InvokeEvent
> (this=0x65e2f0, event=5, callData=0x0, self=0x6429a0) at
> /home/kevin/kitware/VTK/Common/vtkObject.cxx:602
> #130982 0x00007ffff3629705 in vtkObject::InvokeEvent (this=0x6429a0,
> event=5, callData=0x0) at /home/kevin/kitware/VTK/Common/vtkObject.cxx:770
> #130983 0x00007ffff77c7d11 in vtkRenderWindowInteractor::Render
> (this=0x6429a0) at
> /home/kevin/kitware/VTK/Rendering/vtkRenderWindowInteractor.cxx:163
> #130984 0x00007ffff77c97c1 in vtkRenderWindowInteractor::Initialize
> (this=0x6429a0) at
> /home/kevin/kitware/VTK/Rendering/vtkRenderWindowInteractor.cxx:631
> #130985 0x00007ffff697da74 in vtkRenderView::Render (this=0x641f20) at
> /home/kevin/kitware/VTK/Views/vtkRenderView.cxx:305
> #130986 0x00007ffff7dd632b in vtkGeoView2D::Render (this=0x641f20) at
> /home/kevin/kitware/VTK/Geovis/vtkGeoView2D.cxx:116
> #130987 0x00007ffff697dcf8 in vtkRenderView::ProcessEvents
> (this=0x641f20, caller=0x6429a0, eventId=5, callData=0x0) at
> /home/kevin/kitware/VTK/Views/vtkRenderView.cxx:328
> #130988 0x00007ffff6985615 in vtkView::Command::Execute (this=0x641e20,
> caller=0x6429a0, eventId=5, callData=0x0) at
> /home/kevin/kitware/VTK/Views/vtkView.cxx:52
> #130989 0x00007ffff36291f5 in vtkSubjectHelper::InvokeEvent
> (this=0x65e2f0, event=5, callData=0x0, self=0x6429a0) at
> /home/kevin/kitware/VTK/Common/vtkObject.cxx:602
> #130990 0x00007ffff3629705 in vtkObject::InvokeEvent (this=0x6429a0,
> event=5, callData=0x0) at /home/kevin/kitware/VTK/Common/vtkObject.cxx:770
> #130991 0x00007ffff77c7d11 in vtkRenderWindowInteractor::Render
> (this=0x6429a0) at
> /home/kevin/kitware/VTK/Rendering/vtkRenderWindowInteractor.cxx:163
> #130992 0x00007ffff77c97c1 in vtkRenderWindowInteractor::Initialize
> (this=0x6429a0) at
> /home/kevin/kitware/VTK/Rendering/vtkRenderWindowInteractor.cxx:631
> #130993 0x00007ffff77bb913 in vtkRenderWindow::Render (this=0x642640) at
> /home/kevin/kitware/VTK/Rendering/vtkRenderWindow.cxx:264
> #130994 0x00007ffff7dd631f in vtkGeoView2D::Render (this=0x641f20) at
> /home/kevin/kitware/VTK/Geovis/vtkGeoView2D.cxx:114
> #130995 0x0000000000409e11 in TestCoincidentGeoGraphRepresentation2D
> (argc=7, argv=0x7fffffffdae0)
> at
> /home/kevin/kitware/VTK/Geovis/Testing/Cxx/TestCoincidentGeoGraphRepresentation2D.cxx:268
> #130996 0x0000000000408092 in main (ac=7, av=0x7fffffffdae0) at
> /home/kevin/kitware/VTK_OSMesa_Build/Geovis/Testing/Cxx/GeovisCxxTests.cxx:179
>
>
More information about the vtk-developers
mailing list