Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2241 ; Mon, 01 Mar 93 10:50:42 EST Newsgroups: comp.os.386bsd.questions Path: sserve!manuel.anu.edu.au!munnari.oz.au!metro!news From: dawes@physics.su.OZ.AU (David Dawes) Subject: Re: XFree-1.2 crashes w/ xv weather map Message-ID: <1993Feb26.154153.15093@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: <1mc917INN6db@usenet.INS.CWRU.Edu> <1993Feb25.214202.11624@dsuvax.dsu.edu> Date: Fri, 26 Feb 1993 15:41:53 GMT Lines: 47 In article <1993Feb25.214202.11624@dsuvax.dsu.edu> ghelmer@dsuvax.dsu.edu (Guy Helmer) writes: >In <1mc917INN6db@usenet.INS.CWRU.Edu> david@jake.EEAP.CWRU.Edu (David Nerenberg) writes: > >>I was trying to remote display a weather map on my machine and it did >>not like it at all. Bacially, I run xv from another machine authorized >>to display on my screen and X crashes locally, all the way out. At >>least it does re-set the vidio mode back to text! > >I've done some more investigating into this problem and now I'm thoroughly >puzzled. I get the same crash from the XFree86 1.2 color server on my 8MB >40Mhz AMD 80386 at home -- it appears the server gets a signal 4 when xv >is starting up (although I've only been running xv locally). I tried the >running xv under XFree86's server on a 16MB 25Mhz intel 80386 w/ 80387, >and it works fine! The only differences that should count between the two >machines is the amount of RAM and the 80387 chip that the working machine >has; both were using the same ET4000 card and have almost the same amount >of swap. > >I haven't been able to use gdb (either the one supplied with 386BSD or the >recent 4.8 release) on the XFree86 server to get a stack backtrace from >the coredump -- gdb freaks out with an internal error or complains that it >can't access some odd memory location. If you want to improve the trace from the coredump, try adding NoTrapSignals to your Xconfig. It doesn't always help, but often does. The downside of doing this is that the server will not exit gracefully (ie text mode won't be restored). >I just had an idea -- could the 80387 emulator have caused the illegal >instruction trap and killed the X server? Yep, that's it. I did some experimenting with and without the npx driver enabled, and gcc-2.3.3 (which the X dist is compiled with) does generate some fp instructions which aren't handled by the emulator. When such an instruction is encountered, the SIGILL is generated. >Guy Helmer, Dakota State University Computing Services - ghelmer@dsuvax.dsu.edu 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 ------------------------------------------------------------------------------ I was so satisfied, deep down inside, like a hand in a velvet glove -- AC/DC ------------------------------------------------------------------------------