public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com, cygwin@tlinx.org
Subject: Re: X still crashing, but interesting log messages... different config vals needed?
Date: Sun, 12 Feb 2012 19:52:00 -0000 [thread overview]
Message-ID: <4F381871.7080002@dronecode.org.uk> (raw)
In-Reply-To: <4F35EC5C.6050200@tlinx.org>
On 11/02/2012 04:19, Linda Walsh wrote:
> Still crashes in all the places it did 2 months ago, and more, but
> gives more interesting messages in log file (/var/log/xwin/XWin.0.log
I assume this refers to the problem reported in [1], crashing when running
yast2 on SuSE 11.4. I don't know anything about any other crashes you might
have been experiencing.
I haven't done anything specific to try to fix this, because I can't reproduce
the problem and I don't have a useful backtrace.
It would be of great help if you could follow the instructions at [2] to
download the debug symbols and obtain a backtrace of the crash.
> Was wondering if I should be giving any different options that might
> help it behave better?
> Log from last run below --
>
> Welcome to the XWin X Server
> Vendor: The Cygwin/X Project
> Release: 1.11.4.0
> OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
> Package: version 1.11.4-3 built 2012-02-05
>
> XWin was started with the following command line:
>
> /usr/bin/XWin -dpi 101 -multiwindow -clipboard -nowinkill -wm
> [ 14334.463] SocketUNIXAccept: accept() failed
This log looks normal apart from this line.
I don't think this is a new warning, and wasn't in the previous log you
posted, so it's hard to see how this could be directly related to the problem.
On the other hand, I'm a bit surprised that it works at all after that error.
Nevertheless, since UNIX sockets don't seem to be working correctly for you,
you might like to try adding '-nolisten unix' to see if that makes any difference.
On 11/02/2012 03:53, Linda Walsh wrote:
> Re: oh forget the cygcheck...
> (attached)..
cygwin = '() { return 0
}'
While I doubt that is is relevant, that's either a bug in cygcheck or a rather
strange setting for the CYGWIN env var
[1] http://cygwin.com/ml/cygwin-xfree/2011-08/msg00012.html
[2] http://x.cygwin.com/devel/backtrace.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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/
next prev parent reply other threads:[~2012-02-12 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 4:20 Linda Walsh
2012-02-12 19:52 ` Jon TURNEY [this message]
2012-02-12 23:52 ` Linda Walsh
2012-02-13 22:00 ` Jon TURNEY
2012-02-26 20:56 ` Linda Walsh
2012-02-26 16:24 ` Linda Walsh
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=4F381871.7080002@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-xfree@cygwin.com \
--cc=cygwin@tlinx.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 read-only IMAP folder(s) and NNTP newsgroup(s).