Bug 65327

Summary: running gnubik produces a segfault
Product: Mesa Reporter: passer-by <pinode>
Component: Drivers/Gallium/r300Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: bt full

Description passer-by 2013-06-04 05:58:14 UTC
Created attachment 80263 [details]
bt full

X.Org X Server 1.13.3
Fedora release 18 (Spherical Cow)

bash-4.2$ lspci -v|grep ATI
02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV350 AP [Radeon 9600] (prog-if 00 [VGA controller])
02:00.1 Display controller: Advanced Micro Devices [AMD] nee ATI RV350 AP [Radeon 9600] (Secondary)


When I run gnubik (a game), the program segfaults immediately:
bash-4.2$ gnubik 
Segmentation fault (core dumped)
     
bash-4.2$ dmesg|tail -n 1
[ 5769.578454] gnubik[7155]: segfault at 0 ip   (null) sp bfafcbbc
error 4 in gnubik[8048000+16000] 
bash-4.2$ rpm -q gnubik
gnubik-2.4-5.fc18.i686
     
bash-4.2$ gnubik -v|head -n 1
2.4

#0  0x00000000 in ?? ()
#1  0xb217e6f4 in generic_run () from /usr/lib/dri/r300_dri.so
#2  0xb214ae9c in draw_pt_fetch_run_linear ()
from /usr/lib/dri/r300_dri.so

it segfaults on line 646

(gdb) l translate/translate_generic.c:646
641	         copy_size = tg->attrib[attr].copy_size;
642	         if(likely(copy_size >= 0))
643	            memcpy(dst, src, copy_size);
644	         else
645	         {
646	            tg->attrib[attr].fetch( data, src, 0, 0 );
647	
648	            if (0)
649	               debug_printf("Fetch linear attr %d  from %p
stride %d  index %d: " 650	                         " %f, %f,
%f, %f \n", (gdb) 

the bugtrace is attached
Should any additional info be required, I may provide it.
Comment 1 GitLab Migration User 2019-09-18 18:52:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/356.

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.