Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2275 ; Mon, 01 Mar 93 10:51:52 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!emory!ogicse!flop.ENGR.ORST.EDU!gaia.ucs.orst.edu!umn.edu!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Newsgroups: comp.os.386bsd.questions Subject: Re: XFree-1.2 crashes w/ xv weather map Message-ID: <1993Feb26.071851.9900@netcom.com> Date: 26 Feb 93 07:18:51 GMT Article-I.D.: netcom.1993Feb26.071851.9900 References: <1mc917INN6db@usenet.INS.CWRU.Edu> <1993Feb25.214202.11624@dsuvax.dsu.edu> Organization: Netcom Online Communications Services (408-241-9760 login: guest) Lines: 50 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. > >I just had an idea -- could the 80387 emulator have caused the illegal >instruction trap and killed the X server? >-- >Guy Helmer, Dakota State University Computing Services - ghelmer@dsuvax.dsu.edu > Try using xscope on your machine and send us the trace of the packets for both test cases: xv local connection and xv remote. A pain but it can be done, startup your X environment manually and make sure that you start X using gdb. Since, you are accesing the X server from a remote machine I assume that you have telnet access or a dumb terminal. About the gdb not being able to access your stack trace, someone a little while ago posted a fix for gdb to access the core-dump properly. If I find this fix, I will be happy to re-post it. Hope this helps, Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/incoming