public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jerry Lowry <jlowry@edt.com>
To: cygwin-xfree@cygwin.com
Subject: Re: XWin Server Not Starting
Date: Tue, 12 Jan 2010 23:24:00 -0000	[thread overview]
Message-ID: <4B4D048E.5020000@edt.com> (raw)
In-Reply-To: <loom.20100112T205454-522@post.gmane.org>

Well I figured that I would start over.  So, I downloaded the cygwin 
files again to a local disk.  Installed everything from the local disk.  
I found that this time the install did not put any programs in the 
Cyginw-X folder at all.  So I deleted the cygwin download and picked a 
different mirror site.  I found that the number of folders got bigger 
and this time when I installed, the Cygwin-X folder is populated.  ( The 
first site I used was OSU, anyway to ping them to have them upgrade the 
mirror with all of the folders?)

After the install I started the X server.  Worked okay, except that when 
the xterm started it still leaves a blank X windows hanging around.  
Have yet to investigate this, just finished the install.  I then started 
the cygwin dos window and it returned this error:
1 [main] bash 3660 C:\Xwin\bin\bash.exe: *** fatal error - couldn't 
allocate heap, Win32 error 487, base 0x850000, top 0x8B0000, 
reserve_size 389120, allocsize 393216, page_const 4096
2 [main] bash 2848 child_info::sync: wait failed, pid 3660, Win32 error 1812
   1861 [main] bash 2848 fork: child -1 - died waiting for longjmp 
before initialization, retry 0, exit code 0x1000000, errno 11
2 [main] bash 2584 C:\Xwin\bin\bash.exe: *** fatal error - couldn't 
allocate heap, Win32 error 487, base 0x850000, top 0x8B0000, 
reserve_size 389120, allocsize 393216, page_const 4096
301671318 [main] bash 2848 child_info::sync: wait failed, pid 2584, 
Win32 error 1812
301672949 [main] bash 2848 fork: child -1 - died waiting for longjmp 
before initialization, retry 0, exit code 0x1000000, errno 11

I killed the windows after these errors.  I was hoping to check see if 
'sh' was installed, but will look at the xterm instead.
Started the Xterm and got the following error:
/usr/bin/xterm: Could not exec /bin/bash: Bad address

looks like bash needs to be reinstalled or fixed.  Will do the reinstall 
and report back.

thanks

Bob Whitehurst wrote:
> I too had the same problem and I looked through some of the other posts.
> Simon Jean-Francois posted the solution and Andy Koppe posted a followup. Just
> as Andy has suggested, I got a in-use message box because I had a bash shell
> running.
>
> http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00098.html
> http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00099.html
>
>
> --
> 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/
>
>   

--
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:[~2010-01-12 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 14:34 Venkatesan Ekambaram
2010-01-12 20:50 ` Bob Whitehurst
2010-01-12 23:24   ` Jerry Lowry [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=4B4D048E.5020000@edt.com \
    --to=jlowry@edt.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).