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
Cc: Ralf.Oltmanns@financial.com
Subject: Re: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
Date: Mon, 26 May 2014 13:32:00 -0000 [thread overview]
Message-ID: <53834272.4050605@dronecode.org.uk> (raw)
In-Reply-To: <C2AF7B6E9F45034298F4B444248CA6F31F19547733@OB1NWS815.financial.com>
On 26/05/2014 14:18, Ralf Oltmanns wrote:
> I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit).
>
> When trying to start XWin Server, it crashes with signal 11 (Segmentation fault)
>
> My installation is as follows:
> Release: 1.15.0.0
> Package: version 1.15.0-2 built 2014-01-11
Thanks for the bug report.
The current XWin version is 1.15.1-2. Perhaps you could try again with
that?
If that doesn't resolve your problem, I'm afraid that the log doesn't
contain enough information for me to identify the cause of the crash.
Could you then install the xorg-server-debuginfo package, which enables
a more useful backtrace to be generated in the log, and try again?
With 1.15.1, I also enabled a tool I have been working to automate
sending better crash information using minidumps. If you would like to
try that, download it from [1] (anonymous ftp) and put it into /usr/bin
and reproduce your crash again.
[1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe
--
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:[~2014-05-26 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 13:19 Ralf Oltmanns
2014-05-26 13:32 ` Jon TURNEY [this message]
2014-05-26 15:55 ` Ralf Oltmanns
2014-05-27 15:27 ` 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=53834272.4050605@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Ralf.Oltmanns@financial.com \
--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).