Bug 27147

Summary: piglit "fdo23670-drawpix_stencil -auto" test dumps core with RV790
Product: Mesa Reporter: Chris Rankin <rankincj>
Component: Drivers/DRI/R600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium    
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Chris Rankin 2010-03-17 15:44:06 UTC 
Core was generated by `bin/fdo23670-drawpix_stencil -auto'.
Program terminated with signal 11, Segmentation fault.
#0  Process_Export (pAsm=0x23cc660, type=0, 
    export_starting_index=<value optimized out>, export_count=1, 
    starting_register_number=<value optimized out>, is_depth_export=0 '\000')
    at r700_assembler.c:6350
6350	        ucWriteMask = pAsm->pucOutMask[starting_register_number - pAsm->starting_export_register_number];
Missing separate debuginfos, use: debuginfo-install expat-2.0.1-8.fc12.x86_64 glew-1.5.1-3.fc12.x86_64 glibc-2.11.1-1.x86_64 libICE-1.0.6-1.fc12.x86_64 libSM-1.1.0-7.fc12.x86_64 libX11-1.3-1.fc12.x86_64 libXau-1.0.5-1.fc12.x86_64 libXdamage-1.1.2-1.fc12.x86_64 libXext-1.1-2.fc12.x86_64 libXfixes-4.0.4-1.fc12.x86_64 libXi-1.3-2.fc12.x86_64 libXmu-1.0.5-1.fc12.x86_64 libXt-1.0.7-1.fc12.x86_64 libXxf86vm-1.1.0-1.fc12.x86_64 libdrm-2.4.18-0.1.fc12.x86_64 libgcc-4.4.3-4.fc12.x86_64 libjpeg-6b-46.fc12.x86_64 libstdc++-4.4.3-4.fc12.x86_64 libtiff-3.9.2-3.fc12.x86_64 libuuid-2.16.2-7.fc12.x86_64 libxcb-1.5-1.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) print pAsm->pucOutMask[starting_register_number - pAsm->starting_export_register_number]
Cannot access memory at address 0x1023e597e
Comment 1 Andreas Boll 2012-09-11 09:53:44 UTC 
Note: classic r600 driver has been abandoned.

works correctly with r600g (gallium driver) on my rv770
tested with mesa git master e81ee67b51651e99e7e8e52c1ccafc66835d57cd
and mesa 8.0.4

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.