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: boxer@bytezeppelin.com
Subject: Re: XWin 1.12.1.0 seg faults on startup?
Date: Thu, 28 Jun 2012 14:05:00 -0000	[thread overview]
Message-ID: <4FEC6498.5030400@dronecode.org.uk> (raw)
In-Reply-To: <4FEB27C1.7040905@bytezeppelin.com>

On 27/06/2012 16:33, Nick Vasilatos wrote:
>> You might try creating an empty ~/.startxwinrc (so the default xterm is not
>> started by startxwin) and see if that makes a difference?
> 
> Would seem not/seems to fail as before.  See below and log attached.

Okay. thanks for trying anyhow.

This is going to be somewhat problematic to debug since the debugger seems
unable to attach to the faulted process.  I'm not sure what might cause that,
if it's some software you have installed which is interfering with Cygwin or
some security policy you have set?  Are you running XWin under a local
Administrator account?

I've uploaded a new snapshot at [1], can you try running that, adding the
-notrapsignals option to your usual command line.

This should generate a XWin.exe.stackdump file when it crashes.  Can you
attach that to an email, please.

[1] ftp://cygwin.com/pub/cygwinx/XWin.20120628-git-59d15f68d4fd9bb8.exe.bz2

-- 
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/


      reply	other threads:[~2012-06-28 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09 16:33 Nick Vasilatos
2012-06-17 14:09 ` Jon TURNEY
2012-06-21  3:40   ` Nick Vasilatos
2012-06-25 13:35     ` Jon TURNEY
2012-06-27 15:34       ` Nick Vasilatos
2012-06-28 14:05         ` Jon TURNEY [this message]

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=4FEC6498.5030400@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=boxer@bytezeppelin.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).