This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: Cygwin 1.7.22 calls dumper when starting X
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-xfree at cygwin dot com
- Cc: Jim Reisert AD1C <jjreisert at alum dot mit dot edu>
- Date: Wed, 31 Jul 2013 12:58:51 +0100
- Subject: Re: Cygwin 1.7.22 calls dumper when starting X
- References: <CAK-n8j6yg-he-qtugdiirYUMNySms6mNHU0yo3pRz_5xsP1wFA at mail dot gmail dot com>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: cygwin-xfree <cygwin-xfree at cygwin dot com>
On 30/07/2013 18:33, Jim Reisert AD1C wrote:
> I have the latest version of Cygwin (using setup-x86). I see the same
> problem on both 32-bit and 64-bit Windows 7 systems.
>
> CYGWIN_NT-6.1 LTDEN-REISERT 1.7.22(0.268/5/3) 2013-07-22 17:06 i686 Cygwin
>
> Here is how I am starting X:
>
> C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe
>
> When I run this command, a dumper console window pops up with this error:
>
> "failed to open file: No such file or directory"
You're getting the dumper because you have
'error_start=C:\Cygwin\bin\dumper.exe' in your CYGWIN environment variable and
something is crashing...
> I had not seen this before updating setup to setup-x86 and installing
> the latest code. The console window goes away by itself, and XWin
> seems to have started normally, I.e. I get the 'X' in my system tray
> and can launch programs from it.
I can't reproduce this.
Can you try downgrading to run-1.2.0 and see if the problem still exists, that
seems to have caused some people problems [1]
[1] http://cygwin.com/ml/cygwin/2013-07/msg00532.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/