Re: sh.exe: TP_NUM_W_BUFS too small?

[Magnus Holmgren <magnushol at gmail dot com>]

Corinna Vinschen <corinna-cygwin <at> 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