X-Spam-Check-By: sourceware.org
Date: Tue, 22 Nov 2005 19:37:18 -0800
From: Lester Ingber <ingber AT ingber DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: P.S. cygheap base mismatch / popen()
Message-ID: <20051123033718.GA5836@ingber.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.10i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

As I explained in my first posting in this thread, popen() hangs
my code when using the -mn=no-cygwin option under gcc.

Most of the time this happens, I also get printed to STDOUT,
  The process tried to write to a nonexistent pipe.
The xterm window in which I am running the code freezes, and I have to
kill the entire window.

Is there any way this could lead to the cygheap base mismatch problem?

Lester

      +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Yes, I just put in cygwin1-20051117.dll.

The cygheap problem does not seem to be present, and I'm able to start
xterm windows.  A quirk though:  Each xterm window also brings up a
separate DOS window, and thexterm window is killed if I kill the DOS
window?

Thanks.

Lester

: You may want to try again with a snapshot then.
: <http://cygwin.com/snapshots/>
:
: Larry Hall                              http://www.rfk.com



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/