On Thu, Oct 24, 2002 at 02:00:48PM +0200, Michel Dänzer wrote: >On Don, 2002-10-24 at 13:52, Alan Hourihane wrote: >> On Thu, Oct 24, 2002 at 01:47:01PM +0200, Michel Dänzer wrote: >> > > That certainly shouldn't be needed for shared entities. Where exactly >> > > was it crashing ? >> > >> > XAA dereferences pScrn->pScreen to track the state of shared entities. >> > RADEONScreenInit() calls other radeon driver functions which call >> > info->accel->Sync(), but the driver independent code only sets pScrn->pScreen >> > after ScreenInit(). Boom. >> >> A backtrace would be useful.
The backtrace would be useful for showing the exact call sequence leading to the SEGV, and may help in determining if the problem should be fixed in a different way. >If you don't believe me, why don't you just try yourself? As noted in >the comment for that CVS commit, I tracked this down together with Kevin >Puetz, maybe he still has a backtrace somewhere. > >What's the problem with setting this pointer, anyway? If pScrn->pScreen must be dereferenced before the end of ScreenInit, then you need to set it. The driver independent code can't set it before it already does (it isn't allocated yet), so if the driver needs it, it has to do it itself. I think the problem isn't setting this pointer, but making sure that setting it isn't just covering up some other problem. David ------------------------------------------------------- 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
