X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 20 Jul 2009 13:35:44 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sh.exe: TP_NUM_W_BUFS too small?
Message-ID: <20090720113544.GA30066@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20090720T093326-589 AT post DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20090720T093326-589@post.gmane.org>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Jul 20 09:37, Magnus Holmgren wrote:
> When running configure scripts, I sometimes see this error message repeated
> several times, for different lines of the configure script:
> 
> bin\sh.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small.
> 
> I saw this when building libsdl 1.2.13 on Cygwin 1.7 (uname -v reports
> 2009-07-13 10:28) on 64-bit Vista SP2. The configure script seem to have
> succeeded anyway (the build completes and libsdl works). So, is it really
> an error?

Yes, it is definitely a bug.  AFAICS this occurs when a process forks
too deeply (child forks, grandchild forks again, etc, without execing).
The fork() setjmp/longjmp magic accidentally skipped the cleanup
destructor which is supposed to free the temporary thread-local buffers.
This doesn't matter if the child process execs, as usual, but it matters
a lot as soon as the forked child forks further and further, so the
thread-local buffers become a sparse resource.

Thanks for the report.  I'm surprised this hasn't been found earlier.
I'll check in a patch.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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