[Mesa-dev] VTK Offscreen Segfaults

Wed Aug 4 13:46:39 PDT 2010

On 08/04/2010 04:21 PM, tom fogal wrote:
>
> 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...).
>   

The output from valgrind is :

$ valgrind --trace-children=yes 
/home/kevin/kitware/VTK_Build/bin/RenderingCxxTests TestOSConeCxx -D
/home/kevin/kitware/VTKData -T
/home/kevin/kitware/VTK_Build/Testing/Temporary -V
Baseline/Rendering/TestOSConeCxx.png
==5115== Memcheck, a memory error detector
==5115== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==5115== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==5115== Command: /home/kevin/kitware/VTK_Build/bin/RenderingCxxTests
TestOSConeCxx -D /home/kevin/kitware/VTKData -T
/home/kevin/kitware/VTK_Build/Testing/Temporary -V
Baseline/Rendering/TestOSConeCxx.png
==5115==
Mesa: Mesa 7.9-devel DEBUG build Aug  4 2010 15:25:34
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn
compression/decompression unavailable
Mesa: Initializing x86-64 optimizations
Mesa: User error: GL_INVALID_VALUE in glPixelMapusv(mapsize)
==5115== Invalid read of size 1
==5115==    at 0x4A06A68: memcpy (mc_replace_strmem.c:497)
==5115==    by 0x8A7F05F: _mesa_unpack_bitmap (image.c:1215)
==5115==    by 0x8A7F0E8: _mesa_unpack_polygon_stipple (image.c:1140)
==5115==    by 0x8A8B7D4: _mesa_polygon_stipple (polygon.c:202)
==5115==    by 0x8A8BEAA: _mesa_PolygonStipple (polygon.c:222)
==5115==    by 0x5033646: vtkOpenGLRenderWindow::OpenGLInit()
(vtkOpenGLRenderWindow.cxx:242)
==5115==    by 0x508D45D:
vtkXOpenGLRenderWindow::CreateOffScreenWindow(int, int)
(vtkXOpenGLRenderWindow.cxx:951)
==5115==    by 0x508D8DC: vtkXOpenGLRenderWindow::Initialize()
(vtkXOpenGLRenderWindow.cxx:1066)
==5115==    by 0x508DCE2: vtkXOpenGLRenderWindow::Start()
(vtkXOpenGLRenderWindow.cxx:1185)
==5115==    by 0x4F55FC0: vtkRenderWindow::DoStereoRender()
(vtkRenderWindow.cxx:687)
==5115==    by 0x4F55F91: vtkRenderWindow::DoFDRender()
(vtkRenderWindow.cxx:676)
==5115==    by 0x4F55991: vtkRenderWindow::DoAARender()
(vtkRenderWindow.cxx:563)
==5115==  Address 0xb74 is not stack'd, malloc'd or (recently) free'd
==5115==
==5115==
==5115== Process terminating with default action of signal 11 (SIGSEGV)
==5115==  Access not within mapped region at address 0xB74
==5115==    at 0x4A06A68: memcpy (mc_replace_strmem.c:497)
==5115==    by 0x8A7F05F: _mesa_unpack_bitmap (image.c:1215)
==5115==    by 0x8A7F0E8: _mesa_unpack_polygon_stipple (image.c:1140)
==5115==    by 0x8A8B7D4: _mesa_polygon_stipple (polygon.c:202)
==5115==    by 0x8A8BEAA: _mesa_PolygonStipple (polygon.c:222)
==5115==    by 0x5033646: vtkOpenGLRenderWindow::OpenGLInit()
(vtkOpenGLRenderWindow.cxx:242)
==5115==    by 0x508D45D:
vtkXOpenGLRenderWindow::CreateOffScreenWindow(int, int)
(vtkXOpenGLRenderWindow.cxx:951)
==5115==    by 0x508D8DC: vtkXOpenGLRenderWindow::Initialize()
(vtkXOpenGLRenderWindow.cxx:1066)
==5115==    by 0x508DCE2: vtkXOpenGLRenderWindow::Start()
(vtkXOpenGLRenderWindow.cxx:1185)
==5115==    by 0x4F55FC0: vtkRenderWindow::DoStereoRender()
(vtkRenderWindow.cxx:687)
==5115==    by 0x4F55F91: vtkRenderWindow::DoFDRender()
(vtkRenderWindow.cxx:676)
==5115==    by 0x4F55991: vtkRenderWindow::DoAARender()
(vtkRenderWindow.cxx:563)
==5115==  If you believe this happened as a result of a stack
==5115==  overflow in your program's main thread (unlikely but
==5115==  possible), you can try to increase the size of the
==5115==  main thread stack using the --main-stacksize= flag.
==5115==  The main thread stack size used in this run was 10485760.
==5115== Invalid free() / delete / delete[]
==5115==    at 0x4A04D72: free (vg_replace_malloc.c:325)
==5115==    by 0x3E5052CAAA: ??? (in /lib64/libc-2.12.so)
==5115==    by 0x3E5052C641: ??? (in /lib64/libc-2.12.so)
==5115==    by 0x480162B: _vgnU_freeres (vg_preloaded.c:62)
==5115==    by 0xA6DD2CF: ???
==5115==    by 0x8A7F05F: _mesa_unpack_bitmap (image.c:1215)
==5115==    by 0x8A7F0E8: _mesa_unpack_polygon_stipple (image.c:1140)
==5115==    by 0x8A8B7D4: _mesa_polygon_stipple (polygon.c:202)
==5115==    by 0x8A8BEAA: _mesa_PolygonStipple (polygon.c:222)
==5115==    by 0x5033646: vtkOpenGLRenderWindow::OpenGLInit()
(vtkOpenGLRenderWindow.cxx:242)
==5115==    by 0x508D45D:
vtkXOpenGLRenderWindow::CreateOffScreenWindow(int, int)
(vtkXOpenGLRenderWindow.cxx:951)
==5115==    by 0x508D8DC: vtkXOpenGLRenderWindow::Initialize()
(vtkXOpenGLRenderWindow.cxx:1066)
==5115==  Address 0x854f390 is not stack'd, malloc'd or (recently) free'd
==5115==
==5115==
==5115== HEAP SUMMARY:
==5115==     in use at exit: 8,928,115 bytes in 2,120 blocks
==5115==   total heap usage: 2,778 allocs, 659 frees, 9,011,811 bytes
allocated
==5115==
==5115== LEAK SUMMARY:
==5115==    definitely lost: 192 bytes in 1 blocks
==5115==    indirectly lost: 0 bytes in 0 blocks
==5115==      possibly lost: 0 bytes in 0 blocks
==5115==    still reachable: 8,927,923 bytes in 2,119 blocks
==5115==         suppressed: 0 bytes in 0 blocks
==5115== Rerun with --leak-check=full to see details of leaked memory
==5115==
==5115== For counts of detected and suppressed errors, rerun with: -v
==5115== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 6 from 6)
Segmentation fault (core dumped)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20100804/28774d4f/attachment.pgp>