linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: root <whschult@uncc.edu>
To: Michel Ddnzer <daenzerm@student.ethz.ch>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Latest XFree86 v4.0 crashing (possible culprit sawmill)
Date: Fri, 28 Apr 2000 08:50:50 -0400	[thread overview]
Message-ID: <3909892A.41387BC1@uncc.edu> (raw)
In-Reply-To: 39092CEA.1321BC79@student.ethz.ch


> root wrote:
>
> > While switching desktops, X completely dies on me.  It's not
> > consistently repeatable, but I've had to kill the programs it didn't
> > pull with it enough times to know that something's wrong.
> >
> > That's all it's doing.  X dies when I'm switching desktops, either by
> > dragging the mouse, or by clicking the desktop in the deskguide.
>
> Just to be sure: Is this about "real" desktops or virtual desktops? AFAIK
> mouse dragging only works to switch between virtual ones?
>
>
> > Please tell me I'm crazy and that it isn't really happenning...
>
> You're crazy and it isn't really happening. *grin*
>
> Seriously, Sawmill isn't the culprit (Listen people: server crashes are
> _never_ application bugs :) but it seems to point out this server bug better
> than anything else.
>
> If you could provide a gdb backtrace from a static server, that would be
> great, otherwise you could send the log and other useful information either
> here or maybe better to XFree86.
>
>
> Michel


I'm roughly familiar with gdb, but not enough to really know what I
should be doing to help.  Where should I expect to find the core file,
and what information do you need?  Which log file do you need?


Hank

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-04-28 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200004270502.AAA08920@lists.linuxppc.org>
2000-04-28  3:37 ` Latest XFree86 v4.0 crashing (possible culprit sawmill) root
2000-04-28  6:17   ` Michel Dänzer
2000-04-28 12:50     ` root [this message]
2000-04-28 13:29       ` Michel Dänzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3909892A.41387BC1@uncc.edu \
    --to=whschult@uncc.edu \
    --cc=daenzerm@student.ethz.ch \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).