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... -- Mike A. Harris _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
