On Don, 2002-10-24 at 13:53, Felix K�hling wrote: [ backtrace on glutfx exit omitted ]
> I checked radeonDestroyContext. It looks suspicious to me that a lot of > the context is destroyed *before* the RADEON_FIRE_VERTICES macro calls > radeonFlush. I moved RADEON_FIRE_VERTICES before any of the > *_DestroyContext calls and didn't get any more segfaults. A patch is > attached. This might also be a better fix for the texture placeholder heap problem. I was also suspicious about the location of the RADEON_FIREVERTICES() call but thought there might be a reason for it. > Furthermore the segfault occurs in radeonGetLock. Could a segfault in > this place potentially cause a deadlock? No, the lock is released when a client dies. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
