On 08/13/2013 09:50 AM, Brian Paul wrote: > On 08/12/2013 11:30 AM, Kevin H. Hobbs wrote: >> >> --30166-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - >> exiting >> > Well, that's not too helpful.
I think it may have been helpful. Before Valgrind crashed it mentions that osmesa_st_framebuffer_flush_front wrote to an address it should not have. In the test VTK uses a filter that tiles the rendering of a (not very) large image. The render window is initially 150x150 and then after some fooling around magnification is set to 3. I think this results in what I see in gdb : res->width0 = 450 res->height0 = 450 osbuffer->width = 150 bytes = 1800 dst_stride = -600 If I read that last right then in the for loop we write 1800 bytes to dst move back 600 bytes and write another 1800 bytes. Are we overwriting 2/3 of what we just wrote? > Can you send me an executable? Not quickly. > Or, is it > simple to build the test case? > I loose track of what's simple and not for me there's a cron job that just runs a bunch of scripts while I sleep. The test is a python wrapped test so the whole hour long build of vtk is hard to avoid. They are attached for good measure but all I do is: The mesa I use is built nightly with : ./autogen.sh \ --prefix=/home/kevin/mesa_nightly \ --enable-glx \ --enable-dri \ --enable-shared-glapi \ --enable-gallium-llvm \ --with-gallium-drivers=nouveau,swrast \ --enable-osmesa I have VTK cloned : git clone http://vtk.org/VTK.git I happen to be on the nightly-master branch for the dashboard but that shouldn't matter. ctest builds and tests VTK with : ctest -S vtk_osmesa.cmake Since you only want one test a build just like mine is : VTK_BUILD=~/VTK_Build VTK_SRC=~/VTK mkdir $VTK_BUILD cd $VTK_BUILD cmake \ \ -DBUILD_EXAMPLES:BOOL=ON\ -DBUILD_SHARED_LIBS:BOOL=ON\ \ -DVTK_BUILD_ALL_MODULES:BOOL=OFF\ -DVTK_Group_Imaging:BOOL=ON\ -DVTK_Group_MPI:BOOL=ON\ -DVTK_Group_Rendering:BOOL=ON\ -DVTK_Group_StandAlone:BOOL=ON\ -DVTK_Group_Views:BOOL=ON\ \ -DVTK_WRAP_JAVA:BOOL=OFF\ -DVTK_WRAP_PYTHON:BOOL=ON\ -DVTK_WRAP_TCL:BOOL=ON\ \ -DOPENGL_INCLUDE_DIR:PATH=/home/kevin/mesa_nightly/include\ -DOPENGL_gl_LIBRARY:FILEPATH=/home/kevin/mesa_nightly/lib/libGL.so\ -DOPENGL_glu_LIBRARY:FILEPATH=/home/kevin/mesa_nightly/lib/libGLU.so\ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON\ -DOSMESA_INCLUDE_DIR:PATH=/home/kevin/mesa_nightly/include\ -DOSMESA_LIBRARY:FILEPATH=/home/kevin/mesa_nightly/lib/libOSMesa.so\ \ -DVTK_USE_OFFSCREEN:BOOL=ON\ -DVTK_USE_X:BOOL=OFF\ -DVTK_USE_TK:BOOL=OFF\ $VTK_SRC and the test is : $VTK_BUILD/bin/vtkpython "--enable-bt" "$VTK_BUILD/Utilities/vtkTclTest2Py/rtImageTest.py" "$VTK_SRC/Filters/Hybrid/Testing/Python/largeImageOffset.py" "-D" "$VTK_BUILD/ExternalData/Testing" "-T" "$VTK_BUILD/Testing/Temporary" "-V" "$VTK_BUILD/ExternalData/Filters/Hybrid/Testing/Data/Baseline/largeImageOffset.png" "-A" "$VTK_BUILD/Utilities/vtkTclTest2Py" ctest usually downloads the the validation image largeImageOffset.png and the input file mentioned in the test iflamigm.3ds I don't know if this happens without ctest.
# Client maintainer: hob...@ohio.edu
set(CTEST_SITE "bubbles.hooperlab")
set(CTEST_BUILD_NAME "Fedora-18_OSMesaDevel-x86_64")
set(CTEST_CONFIGURATION_TYPE Release)
set(CTEST_CMAKE_GENERATOR "Unix Makefiles")
set( dashboard_model Nightly )
set( CTEST_BUILD_FLAGS -ij8 )
set( CTEST_TEST_ARGS PARALLEL_LEVEL 8 )
set( CTEST_DASHBOARD_ROOT "${CTEST_SCRIPT_DIRECTORY}" )
set( CTEST_SOURCE_DIRECTORY "${CTEST_DASHBOARD_ROOT}/VTK" )
set( CTEST_BINARY_DIRECTORY "${CTEST_DASHBOARD_ROOT}/VTK_OSMesa_Build" )
set( VTK_USE_LARGE_DATA ON )
set( dashboard_cache "
BUILD_EXAMPLES:BOOL=ON
BUILD_SHARED_LIBS:BOOL=ON
VTK_BUILD_ALL_MODULES:BOOL=OFF
VTK_Group_Imaging:BOOL=ON
VTK_Group_MPI:BOOL=ON
VTK_Group_Rendering:BOOL=ON
VTK_Group_StandAlone:BOOL=ON
VTK_Group_Views:BOOL=ON
VTK_WRAP_JAVA:BOOL=OFF
VTK_WRAP_PYTHON:BOOL=ON
VTK_WRAP_TCL:BOOL=ON
OPENGL_INCLUDE_DIR:PATH=/home/kevin/mesa_nightly/include
OPENGL_gl_LIBRARY:FILEPATH=/home/kevin/mesa_nightly/lib/libGL.so
OPENGL_glu_LIBRARY:FILEPATH=/home/kevin/mesa_nightly/lib/libGLU.so
VTK_OPENGL_HAS_OSMESA:BOOL=ON
OSMESA_INCLUDE_DIR:PATH=/home/kevin/mesa_nightly/include
OSMESA_LIBRARY:FILEPATH=/home/kevin/mesa_nightly/lib/libOSMesa.so
VTK_USE_OFFSCREEN:BOOL=ON
VTK_USE_X:BOOL=OFF
VTK_USE_TK:BOOL=OFF
")
include(${CTEST_SCRIPT_DIRECTORY}/VTKScripts/vtk_common.cmake)
update_kitware.sh
Description: application/shellscript
update_mesa.sh
Description: application/shellscript
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
