*BSD News Article 17912


Return to BSD News archive

Xref: sserve comp.os.386bsd.bugs:1041 comp.os.386bsd.questions:3505 comp.windows.x.i386unix:2301 comp.os.386bsd.apps:268
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!mcsun!sun4nl!tuegate.tue.nl!rwc.urc.tue.nl!wmbfmk
From: wmbfmk@rwc.urc.tue.nl (Marc van Kempen)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions,comp.windows.x.i386unix,comp.os.386bsd.apps
Subject: Re: XFree86 1.3 crashes under 386BSD
Date: 3 Jul 1993 17:20:21 +0200
Organization: Eindhoven University of Technology, The Netherlands
Lines: 37
Distribution: world
Message-ID: <wmbfmk.741712328@rwc.urc.tue.nl>
References: <20rq0p$iev@email.tuwien.ac.at>
NNTP-Posting-Host: rwc.urc.tue.nl

mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER) writes:

>One more hint for those who might know the solution: I can trigger a
>crash most easily if I run xlock with one of the modes which draw lines,
>e.g. swarm or qix. Since the precompiled XFree86-1.3 binary has no
>symbols, I can't get a full stack traceback; only the fact that abort()
>was called can be deduced from the core. So most likely some signal
>like bus error et al must have occured.

>Solutions to this problem would be most appreciated!

>- Martin

>P.S. Other setup: 486DX50, 16M mem, 1542B + 300M SCSI, MSoft mouse,
>    etherlink II
>P.P.S. No, it's neither the internal nor the external cache on my
>    motherboard - the server crashes with or without enabling any
>    or both of the two.
Look at the manual page for X386, section BUGS:

BUGS
       There are some graphics bugs that show up when the virtual
       width used is not equal to 1024.

In my setup the server crashes without exception after a few
linedrawings from an arbitrary program, when using a resolution of
1150x900. This never happens when using a resolution of 1024x768. I
suspect that for you, as well as for several others that have reported a
coredump from X386, that here lies the source of your problems.
So when using a resolution different from 1024x768, you can still try to
set the virtual width to 1024 and see what happens.

Greetings,


Marc van Kempen.