From: "Bob Goldberg" <bgoldberg@homeaccess.com>
To: <cygwin@cygwin.com>
Subject: startx-xwin seg fault, signal 11
Date: Wed, 15 Jul 2015 19:57:00 -0000 [thread overview]
Message-ID: <20150715195700.lAc5Xt0yjRevcAD6Mi7i5FzMX_oZM89XRt2AV-q3UIU@z> (raw)
I've been running cygwin/x (x86) under xp pro for YEARS,
with it working perfectly.
The last update to 1.17 has been a disaster.
I've read about using -listen tcp, and DISPLAY=:0.0 ;
however, nothing I've tried resolves the seg fault error i'm getting.
using 1.17.1-5; have also tried 1.17.2-0 to no avail; back on 1-5.
any help or direction would be appreciated!
TIA - Bob
here's a copy of my xwin.log:
>>>
Could not load crashreporter dll
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.17.1.0
OS: CYGWIN_NT-5.1 myxppropc 2.0.4(0.287/5/3) 2015-06-09 12:20 i686
OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32)
Package: version 1.17.1-5 built 2015-06-02
XWin was started with the following command line:
/usr/bin/X :3 -auth /home/bob/.serverauth.4656
ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1440 h 900
winInitializeScreenDefaults - native DPI x 96 y 96
[104131.312] Could not load crashreporter dll
[104131.343] Fatal signal received in thread 0x20000038 [0x1164]
[104131.343] (EE) Segmentation fault at address 0x1
[104131.484] (EE) /usr/bin/xorg-backtrace failed with returncode 0
[104131.484] (EE) Fatal server error:
[104131.484] (EE) Caught signal 11 (Segmentation fault). Server aborting
[104131.484] (EE) Server terminated with error (1). Closing log file.
<<<
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2015-07-15 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 19:57 Bob Goldberg [this message]
[not found] <22057.9358902343$1436990254@news.gmane.org>
2015-07-16 14:55 ` 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=20150715195700.lAc5Xt0yjRevcAD6Mi7i5FzMX_oZM89XRt2AV-q3UIU@z \
--to=bgoldberg@homeaccess.com \
--cc=cygwin@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).