Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1033 comp.windows.x.i386unix:2282 Newsgroups: comp.os.386bsd.bugs,comp.windows.x.i386unix Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!news From: dawes@physics.su.OZ.AU (David Dawes) Subject: Re: Solution (was Re: XFree86 1.3 crashes under 386BSD) Message-ID: <1993Jul2.152401.2726@ucc.su.OZ.AU> Sender: news@ucc.su.OZ.AU Nntp-Posting-Host: physics.su.oz.au Organization: School of Physics, University of Sydney, Australia References: <2114d5$lci@aggedor.rmit.OZ.AU> <1993Jul2.120207.3262@gmd.de> <1993Jul2.135051.4848@cs.utwente.nl> Date: Fri, 2 Jul 1993 15:24:01 GMT Lines: 27 In article <1993Jul2.135051.4848@cs.utwente.nl> sijben@seine.cs.utwente.nl (Paul Sijben) writes: >As mentioned in an earlier article I used the NoSpeedup mode (Xconfig) >and everything works. I can even let xlock use the qix mode! Try using: SpeedUp 55 which only disables the line speedup (55 = 63 - 8). Can anyone who sees this problem run the server under gdb and get some information about the register contents, stack trace, and an assembler listing of the function the crash occurs in? Examining the core is not good enough unless you have NoTrapSignals set in your Xconfig, and in this case, your screen won't be restored. If you run from gdb you can get the info, then continue to get the screen restored. I'm not sure if the standard server binaries are stripped (I don't think so), but if they are you can build an unstripped version with the LinkKit. David -- ------------------------------------------------------------------------------ David Dawes <dawes@physics.su.oz.au> DoD#210 | Phone: +61 2 692 2639 School of Physics, University of Sydney, Australia | Fax: +61 2 660 2903 ------------------------------------------------------------------------------