What does your host.def file look like? What I'm getting at, when you build Xorg 6.9RC2, do you use the Mesa copy in extras or do you point MesaSrcDir at a different Mesa checkout?
Regards, Felix Am Dienstag, den 15.11.2005, 20:39 +0000 schrieb Sergio Monteiro Basto: > On Mon, 2005-11-14 at 12:38 -0800, Ian Romanick wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Sergio Monteiro Basto wrote: > > > On Mon, 2005-11-14 at 07:51 -0800, Ian Romanick wrote: > > >>Sergio Monteiro Basto wrote: > > >> > > >>>Today, I test chromium, tuxracer and foobillard and none of then runs > > >>>try to dig with gdb and all stop on run_texnorm_stage() > > >>> > > >>>here is the debug with backtrace: > > >>> > > >>>Program received signal SIGFPE, Arithmetic exception. > > >>>[Switching to Thread -1208801600 (LWP 12723)] > > >>>0x00ec8a80 in _mesa_test_os_sse_exception_support () from > > >>>/usr/X11R6/lib/modules/dri/savage_dri.so > > >>>(gdb) cont > > >>>Continuing. > > >> > > >>What platform are you running on? Properly built drivers on Linux or > > >>BSD should *NEVER* encounter this code. That code has been removed from > > >>the Linux builds for almost a year. I suspect that you're either > > >>picking up a very old savage_dri.so or something is not right with your > > >>build. > > >> > > >>The code is #ifdef'ed out at line 186 of src/mesa/x86/x86_common.c: > > >> > > >>#if defined(__linux__) && !defined(IN_DRI_DRIVER) > > >> > > >>Clearly, IN_DRI_DRIVER should be defined when building the Savage DRI > > >>driver! :) > > > > > > Hi, > Well I downgrade to xorg-6.9RC1 and the problem disappears, so is a very > recent regression. > About IN_DRI_DRIVE, yes it is defined at all the places. > > With RC1 I still get this "Arithmetic exception" > but 3D apps works without problems. > If I recall correctly this "Arithmetic exception" is not new at all. > > BTW don't know if meters but my laptop is one mobile AMD Athlon(tm) 4 > Processor > > thanks (for your time), > > > > > > I will go investigate this, but this is not the problem because this > > > doesn't stop the app. > > > > That is true, but there are other places in the code that depend on > > IN_DRI_DRIVER being correctly set. If it's not set at this place, it is > > likely that it's not set at the other places either. Having it not set > > in the other places may be the source of the crash. > -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
