[Bug 4087] indirect GLX crashs Xserver / in libGLcore.so ?
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=4087 --- Additional Comments From [EMAIL PROTECTED] 2005-11-15 08:46 --- I bet ctx is null in this case. This patch should do the trick: Index: drivers/x11/xm_dd.c === RCS file: /cvs/xorg/xc/extras/Mesa/src/mesa/drivers/x11/xm_dd.c,v retrieving revision 1.1.1.4 diff -r1.1.1.4 xm_dd.c 568c568,569NewState |= _NEW_BUFFERS; /* to update scissor / window bounds */ --- >if (ctx) > ctx->NewState |= _NEW_BUFFERS; /* to update scissor / window bounds */ Index: main/framebuffer.c === RCS file: /cvs/xorg/xc/extras/Mesa/src/mesa/main/framebuffer.c,v retrieving revision 1.1.1.3 diff -r1.1.1.3 framebuffer.c 312c312,313 NewState |= _NEW_BUFFERS; --- >if (ctx) > ctx->NewState |= _NEW_BUFFERS; -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
-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! :) > > 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. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDePXaX1gOwKyEAw8RAsthAKCDylfGpu3TRt//OysOqLz9Yobp7wCdHdxZ 117LLrZX3AZbrzX8fv+n4MI= =yyn4 -END PGP SIGNATURE- --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
Hi, On Mon, 2005-11-14 at 07:51 -0800, Ian Romanick wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > 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! :) I will go investigate this, but this is not the problem because this doesn't stop the app. the problem is in Program received signal SIGSEGV, Segmentation fault. 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so (gdb) bt #0 0x00c3675b in run_texnorm_stage () from /usr/X11R6/lib/modules/dri/savage_dri.so #1 0x00be2a84 in _tnl_run_pipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #2 0x00c462e9 in savageRunPipeline () from /usr/X11R6/lib/modules/dri/savage_dri.so #3 0x00be7ce6 in _tnl_playback_vertex_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #4 0x00b1f862 in execute_list () from /usr/X11R6/lib/modules/dri/savage_dri.so #5 0x00b1fc5c in _mesa_CallList () from /usr/X11R6/lib/modules/dri/savage_dri.so #6 0x08052d41 in DisplayFunc () at billard3d.c:3015 #7 0x080821d7 in handle_display_event () at sys_stuff.c:90 #8 0x00121a91 in processWindowWorkList (window=0x9f82650) at glut_event.c:1297 #9 0x00122a9b in glutMainLoop () at glut_event.c:1344 #10 0x0805819f in main (argc=1, argv=0xbf93bec4) at billard3d.c:5194 thanks, -- Sérgio M.B. smime.p7s Description: S/MIME cryptographic signature
Re: Cedega & r200 CVS.
Am Sonntag, den 13.11.2005, 20:39 -0500 schrieb Gavriel State: > Felix Kühling wrote: > > >There is a known problem with applications that load libGL dynamically > >with RTLD_LOCAL. Not sure if this is the problem in this case, but the > >symptom (driver not finding a symbol that should be exported by libGL) > >and the fact that it's application-dependent point in that direction. I > >vaguely remember hearing about a Cedega patch for this issue. > > > > > Cedega doesn't load libGL dynamically with RTLD_LOCAL. As Cedega starts > up, it loads some other libraries dynamically with dlopen, and one of > those libraries is command-line-linked to libGL. The libraries that are > loaded with dlopen are opened with RTLD_LAZY. AFAIK RTLD_LOCAL is the default is RTLD_GLOBAL is not specified. (RTLD_LOCAL is defined as 0 in /usr/include/bits/dlfcn.h. ;-) > > What's the origin of this issue on the DRI side, and is it likely to be > fixed in the future? Short answer: no. The DRI drivers are no longer linked against a specific libGL. This is to enable loading of the same driver binaries in different libGLs or the Xserver itself for indirect accelerated rendering. Basically all dependencies on the window system were moved out of the DRI drivers and into libGL. The drivers are not linked against libGL, they just expect that they can magically see symbols from libGL or whoever loaded the driver. When libGL itself is loaded dynamically without RTLD_GLOBAL the driver can't see those symbols and loading fails. > > Take care, > -Gav > Regards, Felix -- | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: problem found with new xorg-6.9RC2 on savage with DRI enabled
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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! :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDeLKTX1gOwKyEAw8RAnU9AJ0cRK94kxW+hLsvcxAfJOco12Zf/gCfToz8 x6nRRgMZIR+pyV4HwaIYzYI= =4Ka3 -END PGP SIGNATURE- --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
