On Sun, Jul 28, 2002 at 04:24:06PM -0700, Mark Vojkovich wrote: > I assume you're using OFfb rather than rivafb. Last time I > tried rivafb I couldn't get it to work reliably.
Correct. I was never able to get rivafb working either. > If it's not that, perhaps you could attach with a debugger and find > out where it's stuck at. It's not really clear from the server > output whether it's in the driver or in the core server. The > stuff it was in the middle of printing out is from the core X-server > code. I can't seem to get any useful info. It seems like maybe something has just gone horribly awry, but I can't really tell since I don't have a lot of experience debugging X servers. I can get GDB to attach to the process and display the stack when the X server is running normally. However, when I try to show the stack of the second instance of the process, this is all I get: Program received signal SIGTSTP, Stopped (user). 0x109adf5c in ?? () (gdb) bt #0 0x109adf5c in ?? () Everything in xc/programs/Xserver/ has been built with debugging symbols, so I am guessing that the stack has been fairly well obliterated if this is all I get. At this point, the X server seems to be spinning, using 100% of available CPU cycles. I hadn't noticed that previously. noah -- _______________________________________________________ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html
msg08061/pgp00000.pgp
Description: PGP signature
