On Fri, 28 Mar 2003, Mark Vojkovich wrote:
I don't suppose you know how to use gdb so you can find
where it crashed at?
Nope, don't know gdb, but that has never stopped me before. (That's what
man and google are for):
# gdb XFree86 ./XFree86.core
GNU gdb 4.18 (FreeBSD)
blahblahblah GPL
That looks much more like a stacktrace (thanks!):
#0 0x28214b78 in kill () from /usr/lib/libc.so.4
#1 0x28255742 in abort () from /usr/lib/libc.so.4
#2 0x806c6e5 in ddxGiveUp ()
#3 0x806c78a in AbortDDX ()
#4 0x80d3de0 in AbortServer ()
#5 0x80d51ad in FatalError ()
#6 0x807f71a in
I would just like to point out a couple other factors as far as
reproducing this, and that it may not be BSD dependent.
We (this is a company machine) bought this PC in a batch from Micron a few
years ago. There were 20-something in the batch, and only 2 diff
models. 1/2 were the Riva128's and
This is only the 4th XFree86 install I've done, and I'm very green to
this. I'm using FreeBSD 4.7, and building this out of the ports tree with
no alterations.
Pretty much, I run -configure, I check out the config file to see if
anything looks erroneous, I start it up with -xf86config and get a
4 matches
Mail list logo
