Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1029 comp.windows.x.i386unix:2275 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!network.ucsd.edu!news.service.uci.edu!balboa.eng.uci.edu!swallace From: swallace@balboa.eng.uci.edu (Steven Wallace) Subject: Re: XFree86 1.3 crashes under 386BSD Nntp-Posting-Host: balboa.eng.uci.edu Message-ID: <2C33DD07.3337@news.service.uci.edu> Newsgroups: comp.os.386bsd.bugs,comp.windows.x.i386unix Organization: University of California, Irvine Lines: 25 Date: 2 Jul 93 07:00:23 GMT References: <20ea6n$5v5@email.tuwien.ac.at> In article <20ea6n$5v5@email.tuwien.ac.at> mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER) writes: >Hello all, > >with so many new goodies arriving lateley, I started to gain some hope >again... anyway, a few months ago when XFree86-1.2 came out, I built >that server from source, and when run it would crash after usually only >a few minutes. Then I tried the precompiled version which exhibited >exactly the same behaviour. There was a short discussion on the >relevant newsgroups pointing out that the most likely problem was in >386BSD itself, but no solution came up, and I had to revert to version 1.1. Yes, I too have had problems with both XFree86 1.2 and 1.3. After running an X application that does a lot of drawing, within a minute or so, I will get a broken pipe and the server will shutdown. In March, I got a 1.2 server version with all the debugging symbols from Richard Murphey. He told me I had to have a FPU, unlike the distribution version (which I do - 486). I was going to do a trace for him using gdb, but interestingly enough, that server never shutdown! So, I have been using the FPU version of XFree86 1.2 ever since. Since the FPU version doesn't crash but the dist version does, it seems to me the problem is somehow related to the FPU code. Any ideas on the problem?