X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SARE_SUB_ENC_UTF8,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Magnus Holmgren Subject: Re: sh.exe: =?utf-8?b?VFBfTlVNX1dfQlVGUw==?= too small? Date: Mon, 20 Jul 2009 11:57:07 +0000 (UTC) Lines: 16 Message-ID: References: <20090720113544 DOT GA30066 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen cygwin.com> writes: > 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. When I looked closer at the script causing the message (not configure as such, but called from configure) it happened in a function that called itself recursively. A few (2-3) levels down the error starts appearing. Magnus -- 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