Re: xf86cfg: ERROR SIGSEGV caught!
SD some fonts can't be displayed any more which worked with freetype1 SD based freetype module Yes. The FreeType 1 library had been fine-tuned to include workarounds for a number of common font bugs (much against David Turner's preferences). These hacks are only now getting into FreeType 2. Now that 4.3 is out, I hope we'll be able to upgrade to 2.1.4; when that happens, I'll be very keen on bug reports describing such failures. Please do not send such bug reports now -- we do know that the version of FreeType included in 4.3 has some limitations. Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Fri, Feb 28, 2003 at 05:46:24AM -0500, Mike A. Harris wrote: On Thu, 27 Feb 2003, Stefan Dirsch wrote: No. Will be some work to extract the CVS diff for me. So you can't reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now before looking deeper into this issue. I've just tried xf86cfg under 4.3 and didn't have any difficulties. One thing I did have to do was clean out ancient drivers from the modules directory -- I had several seg faults until I made sure I didn't have anything older than 4.3 installed. Strange. It only happens if libfreetype.so render module exists. I compile this against system libfreetype to get rid of some bugs in freetype2 which comes with XFree86 (some fonts can't be displayed any more which worked with freetype1 based freetype module). After loading this module every module gets a ERROR SIGSEGV caught! after loading. [...] Loading /usr/X11R6/lib/modules/fonts/libfreetype.so Module freetype: vendor=The XFree86 Project compiled for 4.3.0, module version = 2.0.2 Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so Loading /usr/X11R6/lib/modules/fonts/libtype1.a Module type1: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.2 ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ERROR SIGSEGV caught! Maybe xf86cfg can't handle these modules. XFree86 loader can. Hmm. Perhaps this is related to the setjmp() et al. changes lately? Just a thought... No, I backed these out for testing. Must be related to xf86cfg. Maybe xf86cfg can't handle .so modules. Best regards, Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Fri, Feb 28, 2003 at 05:46:24AM -0500, Mike A. Harris wrote: On Thu, 27 Feb 2003, Stefan Dirsch wrote: No. Will be some work to extract the CVS diff for me. So you can't reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now before looking deeper into this issue. I've just tried xf86cfg under 4.3 and didn't have any difficulties. One thing I did have to do was clean out ancient drivers from the modules directory -- I had several seg faults until I made sure I didn't have anything older than 4.3 installed. Strange. It only happens if libfreetype.so render module exists. I compile this against system libfreetype to get rid of some bugs in freetype2 which comes with XFree86 (some fonts can't be displayed any more which worked with freetype1 based freetype module). After loading this module every module gets a ERROR SIGSEGV caught! after loading. [...] Loading /usr/X11R6/lib/modules/fonts/libfreetype.so Module freetype: vendor=The XFree86 Project compiled for 4.3.0, module version = 2.0.2 Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so Loading /usr/X11R6/lib/modules/fonts/libtype1.a Module type1: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.2 ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ERROR SIGSEGV caught! Maybe xf86cfg can't handle these modules. XFree86 loader can. Hmm. Perhaps this is related to the setjmp() et al. changes lately? Just a thought... Mmm, Mike - did you actually read this thread before making this comment ? Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Fri, 28 Feb 2003, Alan Hourihane wrote: From: Alan Hourihane [EMAIL PROTECTED] To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Subject: Re: xf86cfg: ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libfreetype.so Module freetype: vendor=The XFree86 Project compiled for 4.3.0, module version = 2.0.2 Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so Loading /usr/X11R6/lib/modules/fonts/libtype1.a Module type1: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.2 ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ERROR SIGSEGV caught! Maybe xf86cfg can't handle these modules. XFree86 loader can. Hmm. Perhaps this is related to the setjmp() et al. changes lately? Just a thought... Mmm, Mike - did you actually read this thread before making this comment ? No I did not. I read the message I responded to, which is the only message aside from the one before it in my mail folder. I responded based on that. After your response and reading list archives, it seems that my comment was right on the money too. Was there a particular reason to be rude about my attempt to help, or am I missing something? -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Thu, Feb 27, 2003 at 09:40:00PM +0100, Stefan Dirsch wrote: On Thu, Feb 27, 2003 at 09:51:15AM -0800, Keith Packard wrote: Around 16 o'clock on Feb 27, Stefan Dirsch wrote: No. Will be some work to extract the CVS diff for me. So you can't reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now before looking deeper into this issue. I've just tried xf86cfg under 4.3 and didn't have any difficulties. One thing I did have to do was clean out ancient drivers from the modules directory -- I had several seg faults until I made sure I didn't have anything older than 4.3 installed. Strange. It only happens if libfreetype.so render module exists. I You can potentially run into all sorts of problems using .so modules. If you see the problem with a .a version, then we have a real problem to follow up. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Fri, Feb 28, 2003 at 11:06:49 -0500, Mike A. Harris wrote: On Fri, 28 Feb 2003, Alan Hourihane wrote: From: Alan Hourihane [EMAIL PROTECTED] To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Subject: Re: xf86cfg: ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libfreetype.so Module freetype: vendor=The XFree86 Project compiled for 4.3.0, module version = 2.0.2 Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so Loading /usr/X11R6/lib/modules/fonts/libtype1.a Module type1: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.2 ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ERROR SIGSEGV caught! Maybe xf86cfg can't handle these modules. XFree86 loader can. Hmm. Perhaps this is related to the setjmp() et al. changes lately? Just a thought... Mmm, Mike - did you actually read this thread before making this comment ? No I did not. I read the message I responded to, which is the only message aside from the one before it in my mail folder. I responded based on that. After your response and reading list archives, it seems that my comment was right on the money too. Referring to Stefan's original email you'd have seen he already made the comment about setjmp(). Was there a particular reason to be rude about my attempt to help, or am I missing something? You were just re-stating something that the original poster had already mentioned, and David's followup even asked for Stefan to try reversing the patch anyway to see if the problem resolved itself. Nothing rude about it. Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Thu, Feb 27, 2003 at 12:35:57PM +0100, Stefan Dirsch wrote: Hi Looks like xf86cfg in 4.2.99.902 (most likely also 4.3.0) is broken. At least I see now messages like this. [...] Loading /usr/X11R6/lib/modules/extensions/libGLcore.a Module GLcore: vendor=The XFree86 Project compiled for 4.2.99.902, module version = 1.0.0 ERROR SIGSEGV caught! [...] It also happens for each input and graphics driver. It might be related to this change: 940. Allow xf86setjmp/xf86setlongjmp to work with platforms where setjmp() isn't directly available as a function, specifically Linux platforms that use glibc 2.0 and 2.1. (David Dawes, Keith Packard). I tried to adjust xf86cfg to this change but failed for now. Maybe David or Keith can have a look at this issue? If you tried backing out that change and the problems still shows up, then it's something else. Did you try backing it out? David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
On Thu, Feb 27, 2003 at 09:51:15AM -0800, Keith Packard wrote: Around 16 o'clock on Feb 27, Stefan Dirsch wrote: No. Will be some work to extract the CVS diff for me. So you can't reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now before looking deeper into this issue. I've just tried xf86cfg under 4.3 and didn't have any difficulties. One thing I did have to do was clean out ancient drivers from the modules directory -- I had several seg faults until I made sure I didn't have anything older than 4.3 installed. Strange. It only happens if libfreetype.so render module exists. I compile this against system libfreetype to get rid of some bugs in freetype2 which comes with XFree86 (some fonts can't be displayed any more which worked with freetype1 based freetype module). After loading this module every module gets a ERROR SIGSEGV caught! after loading. [...] Loading /usr/X11R6/lib/modules/fonts/libfreetype.so Module freetype: vendor=The XFree86 Project compiled for 4.3.0, module version = 2.0.2 Unloading /usr/X11R6/lib/modules/fonts/libfreetype.so Loading /usr/X11R6/lib/modules/fonts/libtype1.a Module type1: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.2 ERROR SIGSEGV caught! Loading /usr/X11R6/lib/modules/fonts/libbitmap.a Module bitmap: vendor=The XFree86 Project compiled for 4.3.0, module version = 1.0.0 ERROR SIGSEGV caught! Maybe xf86cfg can't handle these modules. XFree86 loader can. Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
