On Mon, 11 Oct 2004, Huw Jenkins wrote:
> I agree. I can reproduce this problem on my laptop which has an old ATI
> card and a paltry 8Mb of video RAM using the DRI r128 driver. I haven't
> had any crashes on the box here with a GeForce MX 440,
Basically anything that uses hardwre accelerated drivers seems to hit
these problems. The GeForce card probably isn't using its DRI driver? I
think Mesa (which the non-accelerated drivers all use) hides some of the
problems in all its workarounds.
> > Of course it's not obvious whose code is doing the trampling or where it
> > is happening (otherwise we could trivially fix it). Your crash sounded a
> > bit more reproducible (i.e. every time a window was created and was doing
> > the first draw). I can't remember if anyone else has seen that.
>
> Yep, is there any easy way to check what libraries analysis is using (like
> ldd)? I want to make sure that it's not just an mixed up libGL
> situation...
lsof -p pid usually does the trick.
Brian
--
Dr. Brian O. Smith ---------------------- B.Smith at bio.gla.ac.uk
Division of Biochemistry & Molecular Biology,
Institute Biomedical & Life Sciences,
Joseph Black Building, University of Glasgow, Glasgow G12 8QQ, UK.
Tel: 0141 330 5167/6459 Fax: 0141 330 8640
|