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: MBardiaux@mediaxim.be
Subject: Re: XWin 1.12.0-4 crash
Date: Thu, 26 Apr 2012 13:22:00 -0000	[thread overview]
Message-ID: <4F994C0A.2050806@dronecode.org.uk> (raw)
In-Reply-To: <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEC@bespdc01.mediaxim.local>

On 23/04/2012 14:03, Michel Bardiaux wrote:
> Yes, it is a crash at startup.
> 
> I could not find XWin.exe.stackdump anywhere on my hard drive. I have
> attached the bat script (renamed into .txt) used to start cygwin/X,
> maybe I need to modify it.
> 
> Would it work to add 
> 
> CYGWIN='error_start=c:\cygwin\bin\dumper.exe'
> 
> in the system environment (meaning, via the control panel), to have a
> core file that I could then open with gdb?

No, I don't think that would work (for various uninteresting reasons)

Start the X server from a terminal using 'gdb --args XWin -multiwindow', type
'r' to start the X server running, and 'bt full' after it crashes.

-- 
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-04-26 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 13:04 Michel Bardiaux
2012-04-26 13:22 ` Jon TURNEY [this message]
2012-04-26 14:54   ` Michel Bardiaux
2012-04-26 18:20     ` Jon TURNEY
2012-04-27  9:00       ` Michel Bardiaux
  -- strict thread matches above, loose matches on Subject: below --
2012-04-23 11:56 Michel Bardiaux
2012-04-23 12:17 ` 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=4F994C0A.2050806@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=MBardiaux@mediaxim.be \
    --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).