public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Dfficulty with xorg-server-1.17.1-2.
Date: Wed, 25 Feb 2015 13:26:00 -0000	[thread overview]
Message-ID: <CAK-n8j7nHm0uk+gdqeqh5cETACDcvb4qVcN_tLFrKif+PMT79w@mail.gmail.com> (raw)
In-Reply-To: <54ECD29B.7050001@dronecode.org.uk>

On Tue, Feb 24, 2015 at 12:35 PM, Jon TURNEY wrote:

> With regard to the crash problems, can you please try the instructions at
> [1] to generate a backtrace.
>
> [1] http://x.cygwin.com/devel/backtrace.html

This isn't a backtrace, but it's what caused the X server to crash
(while I was at work):

[   164.799] winClipboardProc - winClipboardFlushWindowsMessageQueue
trapped WM_QUIT message, exiting main loop.

I'll follow these steps before I leave for work tomororw.  There is no
specific action, but I'll attach gdb and let it just sit there.

- Generating a backtrace when some specific action is making the X server crash

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  parent reply	other threads:[~2015-02-25  1:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 18:13 GEORGE BARRICK
2015-02-24 19:36 ` Jim Reisert AD1C
2015-02-24 21:39   ` Jon TURNEY
2015-02-24 21:50     ` Jon TURNEY
2015-02-25  1:36       ` GEORGE BARRICK
2015-02-25 17:23         ` GEORGE BARRICK
     [not found]           ` <54F2077C.9080802@dronecode.org.uk>
2015-03-01 14:06             ` GEORGE BARRICK
2015-02-25 13:26     ` Jim Reisert AD1C [this message]
2015-02-25 14:30     ` Jim Reisert AD1C
2015-02-25 17:22       ` Jon TURNEY
2015-02-24 21:44 ` Jon TURNEY

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=CAK-n8j7nHm0uk+gdqeqh5cETACDcvb4qVcN_tLFrKif+PMT79w@mail.gmail.com \
    --to=jjreisert@alum.mit.edu \
    --cc=cygwin-xfree@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).