Robin Redeker wrote: > > Hi, > > i am working on a level editor and when linking > the program with efence, i get a segmentation fault, > here the backtrace: > ----------------------------------------- > #0 scale_internal_ubyte (components=3, widthin=32, heightin=48, > datain=0x4a8b9e00 "\026\021\f%\026", widthout=32, heightout=64, > dataout=0x4aaa6800 "\026\021\f%\026", element_size=1, ysize=96, > group_size=3) at mipmap.c:1473 > #1 0x400f7182 in gluBuild2DMipmapLevelsCore (target=3553, internalFormat=3, > width=32, height=48, widthPowerOf2=32, heightPowerOf2=64, format=6407, > type=5121, userLevel=0, baseLevel=0, maxLevel=6, data=0x4a8b9e00) > at mipmap.c:4127 > #2 0x400f7ee3 in gluBuild2DMipmaps (target=3553, internalFormat=3, width=32, > height=48, format=6407, type=5121, data=0x4a8b9e00) at mipmap.c:4560 > #3 0x08054503 in S_T_AddData24 (tex=0x48823f68, width=32, height=48, > data_x=32, data_y=48, data=0x4a8b9e00 "\026\021\f%\026") > at fe/gl/texture.c:369 > ... rest of programm functions ... > ------------------------------------------ > > Its only occuring when linking to efence. > The program works on others people computers with, for example, nVidias > drivers. So i think, this is a bug in dri libGL. > > I have compiled newest cvs version from today (23.03.2002 12:00 MET) > and installed it. > Using linux kernel 2.4.16 on a AMD Athlon 1400 Mhz with 256 MB RAM. > This is what loading of radeon.o prints to kern.log: > Mar 23 12:36:08 localhost kernel: [drm] AGP 0.99 on VIA Apollo KT133 @ 0xe6000000 >32MB > Mar 23 12:36:08 localhost kernel: [drm] Initialized radeon 1.2.0 20010405 on minor 0 > Its a old radeon 7200 i am using. > > Is this corruption already known ?
I think you had reported this a few months ago. I've been too busy to look into it. This isn't a DRI bug or a Mesa bug. It's in the SGI GLU code. Somebody will just have to roll up their sleeves and investigate. It shouldn't be too hard to figure our. You should at least try recompiling the GLU library (get it from the Mesa distro) with -g and examine the instruction that's causing the segfault. Is it a read or write problem, for example? -Brian _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
