X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.0 required=5.0	tests=BAYES_40,RCVD_IN_DNSWL_NONE
X-Spam-Check-By: sourceware.org
Message-ID: <4C0C685A.1010803@x-ray.at>
Date: Mon, 07 Jun 2010 05:32:42 +0200
From: Reini Urban <rurban AT x-ray DOT at>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.9) Gecko/20100317 SeaMonkey/2.0.4
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
References: <20100603004331 DOT eehneofq8kos4ccw AT webmail DOT 12000 DOT org> <4C07FC62 DOT 90207 AT 12000 DOT org> <20100604083653 DOT GA6401 AT calimero DOT vinschen DOT de> <4C08CAE9 DOT 2000507 AT 12000 DOT org> <4C08D2B8 DOT 8090609 AT 12000 DOT org>
In-Reply-To: <4C08D2B8.8090609@12000.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Nasser M. Abbasi schrieb:
> On 6/4/2010 2:44 AM, Nasser M. Abbasi wrote:
>> On 6/4/2010 1:36 AM, Corinna Vinschen wrote:
>>>>
>>>> Error: Cannot read 'img2.png': No such file or directory
>>>> Converting image #1
>>>> 0 [main] perl 3400 C:\cygwin\bin\perl.exe: *** fatal error -
>>>> Internal error: TP_NUM_W_BUFS too small."
>>>
>>
>>> This looks like an internal error in Cygwin which runs out of TLS
>>> filename buffers. For a start, could you please strace the perl
>>> process? This may help to figure out the function in which the problem
>>> occurs.
>>>
>>>
>>> Corinna
>>>
>>
>
>>
>> $ export PERLDB_OPTS="NonStop frame=2"
>> make test
>>
>
> I got a little more useful output using this:
>
> $export PERLDB_OPTS="NonStop AutoTrace frame=2"
> $ make test >& out.txt

PERLDB_OPTS is only for the perl debugger, which you don't run I suppose.
Corinna wanted a strace for perl, around the section where the fork 
fails. It must not be the whole 2GB.

To build a debugging perl you'd need the source package and run
./build --debug
But this won't be needed I suppose, as it's a cygwin error around fork.

> Looking at out.txt, the output around the crash is below. It seems to
> come after exec($cmd). It looks like it can't spawn a new process.
>
> btw, this is windows 7. new PC, 8 GM ram.

UAC already tried to disable?

> If you need the complete file out.txt, I can send it to you directly.
>
> thanks
> --Nasser
>
> =========
>
> 262: my ($self,$cmd,$in,$out,$err) = @_;
> 263: carp qq{Debug (syswait): Running "$cmd"\n} if($Verbose);
> 265: my $status;
> 266: my $child_pid;
> 267: if ($child_pid = fork) {

You can try to add a small sleep here after line 267, the fork.
        sleep(0.2);

> 268: $status = waitpid($child_pid, 0);
> ######### Forked, but do not know how to create a new TTY. #########
> Since two debuggers fight for the same TTY, input is severely entangled.
>
> I know how to switch the output to a different window in xterms, OS/2
> consoles, and Mac OS X Terminal.app only. For a manual switch, put the name
> of the created TTY in $DB::fork_TTY, or define a function
> DB::get_fork_TTY() returning this.
>
> On UNIX-like systems one can get the name of a TTY for the given window
> by typing tty, and disconnect the shell from TTY by sleep 1000000.
>
> 274: unless(exec($cmd)) {
> 0 [main] perl 4524 C:\cygwin\bin\perl.exe: *** fatal error - Internal
> error: TP_NUM_W_BUFS too small.
> 269: carp "Debug (syswait): Finished child process: #$child_pid\n"
> 270: if($Verbose);
> 271: $child_pid = 0;
> 272: return($?);
> exited L2hos::Unix::syswait
>
> Error while converting image
> 4239: if (! -r "${PREFIX}$img") {
> 4240: &write_warnings("\nFailed to convert image $psname.ps")
> ========================
>
> --
> Problem reports: http://cygwin.com/problems.html

We haven't got this report, BTW.

Also, where do have your latex2html from?

-- 
Reini Urban
http://phpwiki.org/  http://murbreak.at/

--
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