Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Sat, Jun 19, 2010 at 11:25:53PM -0400, Christopher Faylor wrote: On Fri, Jun 18, 2010 at 01:51:37AM -0400, Christopher Faylor wrote: On Fri, Jun 18, 2010 at 12:49:09AM -0500, Yaakov (Cygwin/X) wrote: On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xgettext and msgfmt) when building the documentation examples. I doubt that helps you much, and I have been unable to get a STC unsimplified enough to not work. (If that makes any sense.) That makes a certain amount of sense since the error is due to path manipulation and gettext and msgfmt would be doing a lot of it. Running under gdb did not show a crash in python, but I was able to capture an strace of a failure. Let me know if that will be helpful. Sure. Send it to me in private email please. me at myinitials dot cx . Yaakov, if you sent this, I never got it. Got it. Thanks Yaakov. I see exactly what the problem is but I don't yet know how to fix it. Still pondering. cgf -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Mon, Jun 21, 2010 at 12:44:55PM -0400, Christopher Faylor wrote: On Sat, Jun 19, 2010 at 11:25:53PM -0400, Christopher Faylor wrote: On Fri, Jun 18, 2010 at 01:51:37AM -0400, Christopher Faylor wrote: On Fri, Jun 18, 2010 at 12:49:09AM -0500, Yaakov (Cygwin/X) wrote: On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xgettext and msgfmt) when building the documentation examples. I doubt that helps you much, and I have been unable to get a STC unsimplified enough to not work. (If that makes any sense.) That makes a certain amount of sense since the error is due to path manipulation and gettext and msgfmt would be doing a lot of it. Running under gdb did not show a crash in python, but I was able to capture an strace of a failure. Let me know if that will be helpful. Sure. Send it to me in private email please. me at myinitials dot cx . Yaakov, if you sent this, I never got it. Got it. Thanks Yaakov. I see exactly what the problem is but I don't yet know how to fix it. Still pondering. Yaakov's problem should be fixed in the latest snapshot. Given the nature of the problem, it is possible that there are other cases lurking. So, please try the snapshot and, if you still see the problem, Cygwin will now produce a stackdump file. If so, please send it along here. It's not going to be very large. http://cygwin.com/snapshots/ cgf -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
Christopher Faylor schrieb: On Fri, Jun 18, 2010 at 01:51:37AM -0400, Christopher Faylor wrote: On Fri, Jun 18, 2010 at 12:49:09AM -0500, Yaakov (Cygwin/X) wrote: On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xgettext and msgfmt) when building the documentation examples. I doubt that helps you much, and I have been unable to get a STC unsimplified enough to not work. (If that makes any sense.) That makes a certain amount of sense since the error is due to path manipulation and gettext and msgfmt would be doing a lot of it. Running under gdb did not show a crash in python, but I was able to capture an strace of a failure. Let me know if that will be helpful. Sure. Send it to me in private email please. me atmyinitials dot cx . Yaakov, if you sent this, I never got it. Here is the src package: http://mirrors.kernel.org/sources.redhat.com/cygwinports/tmp-py26/Java/java-gnome4.0/ -- Reini -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Fri, Jun 18, 2010 at 01:51:37AM -0400, Christopher Faylor wrote: On Fri, Jun 18, 2010 at 12:49:09AM -0500, Yaakov (Cygwin/X) wrote: On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xgettext and msgfmt) when building the documentation examples. I doubt that helps you much, and I have been unable to get a STC unsimplified enough to not work. (If that makes any sense.) That makes a certain amount of sense since the error is due to path manipulation and gettext and msgfmt would be doing a lot of it. Running under gdb did not show a crash in python, but I was able to capture an strace of a failure. Let me know if that will be helpful. Sure. Send it to me in private email please. me at myinitials dot cx . Yaakov, if you sent this, I never got it. cgf -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Fri, 2010-06-04 at 10:36 +0200, Corinna Vinschen wrote: 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. I'll bring this to your attention: http://www.cygwin.com/ml/cygwin/2009-07/msg00710.html FWIW, I'm also seeing this -- but not with perl -- in the context of fork(), where the actual commands work just fine manually. Yaakov -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Thu, Jun 17, 2010 at 04:33:42PM -0500, Yaakov (Cygwin/X) wrote: On Fri, 2010-06-04 at 10:36 +0200, Corinna Vinschen wrote: 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. I'll bring this to your attention: http://www.cygwin.com/ml/cygwin/2009-07/msg00710.html FWIW, I'm also seeing this -- but not with perl -- in the context of fork(), where the actual commands work just fine manually. Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. Barring that can you try building a version of the dll with TP_NUM_W_BUFS set to 11, 12, 13, etc. to see if that fixes the problem? It is barely possible that the number is too small now. I don't see how fork would exacerbate any problem here as Corinna concluded in the email that you cite since it seems like no destructors would or should ever be called by fork(). cgf -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xgettext and msgfmt) when building the documentation examples. I doubt that helps you much, and I have been unable to get a STC unsimplified enough to not work. (If that makes any sense.) Running under gdb did not show a crash in python, but I was able to capture an strace of a failure. Let me know if that will be helpful. Yaakov -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Fri, Jun 18, 2010 at 12:49:09AM -0500, Yaakov (Cygwin/X) wrote: On Thu, 2010-06-17 at 18:31 -0400, Christopher Faylor wrote: Do you have a test case? I tried to make one but it didn't fail for me. If you can generate a test case I'm sure I could fix the problem. The only place I see it consistently is when the java-gnome build calls gettext's tools (xgettext and msgfmt) when building the documentation examples. I doubt that helps you much, and I have been unable to get a STC unsimplified enough to not work. (If that makes any sense.) That makes a certain amount of sense since the error is due to path manipulation and gettext and msgfmt would be doing a lot of it. Running under gdb did not show a crash in python, but I was able to capture an strace of a failure. Let me know if that will be helpful. Sure. Send it to me in private email please. me at myinitials dot cx . cgf -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
There is a similar post from 2009 where the conclusion is that this can be caused by very deep forking (http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it possible that the make script does very deep, or is stuck in infinite, recursion? On 6/8/10, Nasser M. Abbasi n...@12000.org wrote: On 6/7/2010 7:03 PM, Charles Wilson wrote: On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote: $ make test 0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. I wonder if the 'test' procedure for latex2hmtl sets the $PATH to your installed LaTeX implementation. Or worse, somehow sets a PERL5_INCPATH variable to point at the perl/lib/ directory under G:\LATEX\. If THAT happened, then your cygwin-perl would be trying to use native-perl's libraries (including binary extensions)... Try, temporarily, moving G:/LATEX/perl out of the way. -- Chuck Ok, I did. I renamed my windows perl folder, but I still get the same error. May be someone can try to install Latex2html on their cygwin as I did and try this? May be this has nothing to do with windows 64 bit or windows 7, so any windows version might show this problem as well? Installation of l2h is easy on cygwin, just need to download l2h and untar and type ./configure, make, make install, make test Instructions how to install l2h on cygwin are on my page below: http://12000.org/my_notes/l2hwin/index.htm (need to edit one file, to make sure to tell l2h is under Unix) Not many people use l2h under cygwin, may be I am the first to try to do this on cygwin 1.7? == $ ls /cygdrive/G/LATEX | grep -i perl perl_NOT_USED_FOR_MINUTE $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ which perl /usr/bin/perl $ perl -v This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int (with 12 registered patches, see perl -V for more detail) $ make test Converting image #2 0 [main] perl 4396 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 712 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. == --Nasser -- 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 -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
Err, 'very deep' was a bit misleading, the error seemed to show up at 2-3 levels according to the last post in that thread. On 6/8/10, Alexander T mittspamko...@gmail.com wrote: There is a similar post from 2009 where the conclusion is that this can be caused by very deep forking (http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it possible that the make script does very deep, or is stuck in infinite, recursion? On 6/8/10, Nasser M. Abbasi n...@12000.org wrote: On 6/7/2010 7:03 PM, Charles Wilson wrote: On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote: $ make test 0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. I wonder if the 'test' procedure for latex2hmtl sets the $PATH to your installed LaTeX implementation. Or worse, somehow sets a PERL5_INCPATH variable to point at the perl/lib/ directory under G:\LATEX\. If THAT happened, then your cygwin-perl would be trying to use native-perl's libraries (including binary extensions)... Try, temporarily, moving G:/LATEX/perl out of the way. -- Chuck Ok, I did. I renamed my windows perl folder, but I still get the same error. May be someone can try to install Latex2html on their cygwin as I did and try this? May be this has nothing to do with windows 64 bit or windows 7, so any windows version might show this problem as well? Installation of l2h is easy on cygwin, just need to download l2h and untar and type ./configure, make, make install, make test Instructions how to install l2h on cygwin are on my page below: http://12000.org/my_notes/l2hwin/index.htm (need to edit one file, to make sure to tell l2h is under Unix) Not many people use l2h under cygwin, may be I am the first to try to do this on cygwin 1.7? == $ ls /cygdrive/G/LATEX | grep -i perl perl_NOT_USED_FOR_MINUTE $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ which perl /usr/bin/perl $ perl -v This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int (with 12 registered patches, see perl -V for more detail) $ make test Converting image #2 0 [main] perl 4396 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 712 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. == --Nasser -- 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 -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/8/2010 12:46 AM, Alexander T wrote: There is a similar post from 2009 where the conclusion is that this can be caused by very deep forking (http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it possible that the make script does very deep, or is stuck in infinite, recursion? Yes, I know, I saw the above, and I did point that message when I first reported the problem: http://readlist.com/lists/cygwin.com/cygwin/8/44577.html May be then this bug has been there for a year now. --Nasser -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Jun 8 00:54, Nasser M. Abbasi wrote: On 6/8/2010 12:46 AM, Alexander T wrote: There is a similar post from 2009 where the conclusion is that this can be caused by very deep forking (http://readlist.com/lists/cygwin.com/cygwin/6/34359.html). Is it possible that the make script does very deep, or is stuck in infinite, recursion? Yes, I know, I saw the above, and I did point that message when I first reported the problem: http://readlist.com/lists/cygwin.com/cygwin/8/44577.html May be then this bug has been there for a year now. You missed http://readlist.com/lists/cygwin.com/cygwin/6/34365.html This bug has been fixed for a year now. Your bug is something else. I'm still waiting for some helpful debugging like an strace or, even better, a simple testcase in plain C. 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/8/2010 1:25 AM, Corinna Vinschen wrote: Your bug is something else. I'm still waiting for some helpful debugging like an strace or, even better, a simple testcase in plain C. Corinna If someone using windows 7 out there, can install Latex2html with the current cygwin, they should be able to reproduce this bug (may be this is already done, I do not know). If they can't reproduce it, then this means there is something else on my PC which is causing it. --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
2010/6/7 Nasser M. Abbasi n...@12000.org: On 6/6/2010 8:32 PM, Reini Urban wrote: -- Problem reports: http://cygwin.com/problems.html We haven't got this report, BTW. Hello Rieni; I went to make a report, but not able to find where to do that. I went in circles looking for a link. At the link above you'll see in bold Run cygcheck -s -v -r cygcheck.out and include cygcheck.out as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a straight text file so that it can be easily viewed. So that we can you see your environment. But what I did is document it all here, under the cygwin section http://12000.org/my_notes/l2hwin/index.htm Please feel free to use this as the report. Great. So it looks like we can make cygwin even more slower, eh, fix that in perl core for Win64 cygwin only, to sleep some milliseconds after a fork. We I need a confirmation because I cannot repro it. Do you have any process hook application running, such as an antivir SW listed in BLODA? http://cygwin.com/faq/faq.using.html#faq.using.bloda -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 12:46 AM, Reini Urban wrote:
2010/6/7 Nasser M. Abbasin...@12000.org:
On 6/6/2010 8:32 PM, Reini Urban wrote:
--
Problem reports: http://cygwin.com/problems.html
At the link above you'll see in bold
Run cygcheck -s -v -r cygcheck.out and include cygcheck.out as an
attachment in your report.
Ok. But where to email the actual attachment and the report?? That is
what I am confused about. To this mailing list (cygwin@cygwin.com)?
But what I did is document it all here, under the cygwin section
http://12000.org/my_notes/l2hwin/index.htm
Please feel free to use this as the report.
Great.
So it looks like we can make cygwin even more slower,
eh, fix that in perl core for Win64 cygwin only,
to sleep some milliseconds after a fork.
We I need a confirmation because I cannot repro it.
Ok, I changed sleep, kept making it sleep longer and longer, up to
sleep(100), and the problem still there:
===
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) {
268: sleep(100);
# 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 100.
275: unless(exec($cmd)) {
0 [main] perl 3748 C:\cygwin\bin\perl.exe: *** fatal error -
Internal error: TP_NUM_W_BUFS too small.
269: $status = waitpid($child_pid, 0);
270: carp Debug (syswait): Finished child process:
#$child_pid\n
271: if($Verbose);
272: $child_pid = 0;
273: return($?);
==
Do you have any process hook application running,
such as an antivir SW listed in BLODA?
http://cygwin.com/faq/faq.using.html#faq.using.bloda
Yes, I have NOD32 Antivirus, 64 bit version running on my PC. Version
4.2.4, windows 7 home premium 64 bit on intel i7-930.
btw, That list seems to list every anti-virus software out there :)
I'll go turn off nod32 real time protection now for one minute while I
run the test again to see if it makes a difference
ok, I am back.
Turned off nod32, run the test, and the problem is STILL there.
thanks
--Nasser
--
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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Mon, Jun 07, 2010 at 11:48:54AM -0700, Nasser M. Abbasi wrote: This is a bug report. attached is output of cygcheck -s -v -r (I get some access denited warnings btw): $ cygcheck -s -v -r cygcheck.out /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5 Access is denied. $ This looks suspicious: Warning: C:\cygwin\bin\perl.exe hides G:\LATEX\perl\bin\perl.exe That would indicate that you have two versions of perl on your system. cgf -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 12:41 PM, Christopher Faylor wrote: On Mon, Jun 07, 2010 at 11:48:54AM -0700, Nasser M. Abbasi wrote: This is a bug report. attached is output of cygcheck -s -v -r (I get some access denited warnings btw): $ cygcheck -s -v -r cygcheck.out /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5 Access is denied. $ This looks suspicious: Warning: C:\cygwin\bin\perl.exe hides G:\LATEX\perl\bin\perl.exe That would indicate that you have two versions of perl on your system. cgf Yes, I have the windows version of perl (Active Perl 5.1) and cygwin own perl. What is wrong with this? I need the windows version to be able to use latex2html on windows, since I am not able to use latex2html installed on cygwin. Can't one install different perl on windows if they have cygwin with its own perl? cygwin perl comes before windows perl. windows perl is on windows path (defined by using windows, outside cygwin). $ echo $PATH /usr/local/bin:/usr/bin:/bin:/cygdrive/g/LATEX/MiKTeX2.8/miktex/bin:/cygdrive/g/ LATEX/GnuWin32/bin:/cygdrive/g/LATEX/latex2html/bin:/cygdrive/g/LATEX/perl/bin:/ cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbe m:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0/:/cygdrive/c/Program Files (x86)/ATI Technologies/ATI.ACE/Core-Static:/cygdrive/c/Program Files (x86)/MATL AB/R2008b Student/bin:/cygdrive/c/Program Files (x86)/MATLAB/R2008b Student/bin/ win32:/usr/lib/lapack m...@me-pc ~ $ which perl /usr/bin/perl --Nasser -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Mon, Jun 07, 2010 at 12:59:51PM -0700, Nasser M. Abbasi wrote: On 6/7/2010 12:41 PM, Christopher Faylor wrote: On Mon, Jun 07, 2010 at 11:48:54AM -0700, Nasser M. Abbasi wrote: This is a bug report. attached is output of cygcheck -s -v -r (I get some access denited warnings btw): $ cygcheck -s -v -r cygcheck.out /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5 Access is denied. $ This looks suspicious: Warning: C:\cygwin\bin\perl.exe hides G:\LATEX\perl\bin\perl.exe That would indicate that you have two versions of perl on your system. Yes, I have the windows version of perl (Active Perl 5.1) and cygwin own perl. What is wrong with this? I need the windows version to be able to use latex2html on windows, since I am not able to use latex2html installed on cygwin. Can't one install different perl on windows if they have cygwin with its own perl? cygwin perl comes before windows perl. windows perl is on windows path (defined by using windows, outside cygwin). $ echo $PATH /usr/local/bin:/usr/bin:/bin:/cygdrive/g/LATEX/MiKTeX2.8/miktex/bin:/cygdrive/g/ LATEX/GnuWin32/bin:/cygdrive/g/LATEX/latex2html/bin:/cygdrive/g/LATEX/perl/bin:/ cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbe m:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0/:/cygdrive/c/Program Files (x86)/ATI Technologies/ATI.ACE/Core-Static:/cygdrive/c/Program Files (x86)/MATL AB/R2008b Student/bin:/cygdrive/c/Program Files (x86)/MATLAB/R2008b Student/bin/ win32:/usr/lib/lapack Rather than express amazement that I raised the issue why not just prove that this doesn't mean anything by simplifying your path and trying again? I would try just doing something like: c:\set PATH=c:\cygwin\bin;c:\windows;c:\windows\system32;c:\windows\system32\Wbem bash$ ... I also meant to mention that you should remove the reference to /usr/bin since /bin and /usr/bin are the same directory under Cygwin. This won't have any effect other than to make things slightly slower but you don't need to have this in your path. cgf -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 1:15 PM, Christopher Faylor wrote: Rather than express amazement that I raised the issue why not just prove that this doesn't mean anything by simplifying your path and trying again? I am not expressing amazement, I was asking a simple question, if one can't install windows perl if they have cygwin also. btw, I did NOT touch the $PATH. This is how it is out of the box. cygwin by default post-append windows PATH to /usr/bin:/bin:. In my $HOME/.barc I only add /usr/loca/bin to PATH I would try just doing something like: c:\set PATH=c:\cygwin\bin;c:\windows;c:\windows\system32;c:\windows\system32\Wbem bash$ ... Ok, I just did, and those warnings are still there: $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ cygcheck -s -v -r cygcheck.out /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5 Access is denied. $ --Nasser I also meant to mention that you should remove the reference to /usr/bin since /bin and /usr/bin are the same directory under Cygwin. This won't have any effect other than to make things slightly slower but you don't need to have this in your path. cgf -- 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 -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 4:34 PM, Nasser M. Abbasi wrote: On 6/7/2010 1:15 PM, Christopher Faylor wrote: Rather than express amazement that I raised the issue why not just prove that this doesn't mean anything by simplifying your path and trying again? I am not expressing amazement, I was asking a simple question, if one can't install windows perl if they have cygwin also. You can. But if you're having a problem, it makes sense to eliminate the possible collision, no? I would try just doing something like: c:\set PATH=c:\cygwin\bin;c:\windows;c:\windows\system32;c:\windows\system32\Wbem bash$ ... Ok, I just did, and those warnings are still there: $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ cygcheck -s -v -r cygcheck.out /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 ... Chris wasn't asking you to try this to see if the cygcheck warnings would go away. He was asking you to try this to see if it made any difference with your original problem. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Mon, Jun 07, 2010 at 01:34:21PM -0700, Nasser M. Abbasi wrote: On 6/7/2010 1:15 PM, Christopher Faylor wrote: Rather than express amazement that I raised the issue why not just prove that this doesn't mean anything by simplifying your path and trying again? I am not expressing amazement, I was asking a simple question, if one can't install windows perl if they have cygwin also. btw, I did NOT touch the $PATH. This is how it is out of the box. So it is. I'm pretty dense for never noticing this after all of these years. cygwin by default post-append windows PATH to /usr/bin:/bin:. In my $HOME/.barc I only add /usr/loca/bin to PATH I would try just doing something like: c:\set PATH=c:\cygwin\bin;c:\windows;c:\windows\system32;c:\windows\system32\Wbem bash$ ... Ok, I just did, and those warnings are still there: $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ cygcheck -s -v -r cygcheck.out /usr/bin/cygrunsrv: warning: OpenService failed for 'DcomLaunch': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': Win32 error 5 Access is denied. /usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5 Access is denied. $ As Larry suggests, I wasn't referring to the cygcheck warnings. I was referring to your bug report. -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 2:13 PM, Larry Hall (Cygwin) wrote: Chris wasn't asking you to try this to see if the cygcheck warnings would go away. He was asking you to try this to see if it made any difference with your original problem. OK, I just did. The perl crash is still there. Please let me know if anything else I can try. === $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ ./configure creating cache ./config.cache checking for perl... /usr/bin/perl checking whether #! works in shell scripts... yes . $ make $ make install /usr/bin/perl config/install.pl install.pl (Revision 1.12) Info: Installed /usr/local/share/lib/latex2html/icons/blueball.gif Info: Installed /usr/local/share/lib/latex2html/icons/blueball.png mktexlsr: Updating /var/cache/fonts/ls-R... mktexlsr: Updating /var/lib/texmf/ls-R... mktexlsr: Done. Done. Have a lot of fun with LaTeX2HTML! $ $ make test 0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. ... === Also tried with adding sleep(3) as was earlier suggested, and repated all the above, same problem. --Nasser -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote: $ make test 0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. I wonder if the 'test' procedure for latex2hmtl sets the $PATH to your installed LaTeX implementation. Or worse, somehow sets a PERL5_INCPATH variable to point at the perl/lib/ directory under G:\LATEX\. If THAT happened, then your cygwin-perl would be trying to use native-perl's libraries (including binary extensions)... Try, temporarily, moving G:/LATEX/perl out of the way. -- Chuck -- 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
Re: bug report: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/7/2010 7:03 PM, Charles Wilson wrote: On 6/7/2010 8:49 PM, Nasser M. Abbasi wrote: $ make test 0 [main] perl 5308 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 4824 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. I wonder if the 'test' procedure for latex2hmtl sets the $PATH to your installed LaTeX implementation. Or worse, somehow sets a PERL5_INCPATH variable to point at the perl/lib/ directory under G:\LATEX\. If THAT happened, then your cygwin-perl would be trying to use native-perl's libraries (including binary extensions)... Try, temporarily, moving G:/LATEX/perl out of the way. -- Chuck Ok, I did. I renamed my windows perl folder, but I still get the same error. May be someone can try to install Latex2html on their cygwin as I did and try this? May be this has nothing to do with windows 64 bit or windows 7, so any windows version might show this problem as well? Installation of l2h is easy on cygwin, just need to download l2h and untar and type ./configure, make, make install, make test Instructions how to install l2h on cygwin are on my page below: http://12000.org/my_notes/l2hwin/index.htm (need to edit one file, to make sure to tell l2h is under Unix) Not many people use l2h under cygwin, may be I am the first to try to do this on cygwin 1.7? == $ ls /cygdrive/G/LATEX | grep -i perl perl_NOT_USED_FOR_MINUTE $ echo $PATH /usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem $ which perl /usr/bin/perl $ perl -v This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int (with 12 registered patches, see perl -V for more detail) $ make test Converting image #2 0 [main] perl 4396 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image: No such file or directory Error: Cannot read 'img2.png': No such file or directory Converting image #1 0 [main] perl 712 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. == --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
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 100.
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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/6/2010 8:32 PM, Reini Urban wrote:
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.
Ok, thanks for letting me know.
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?
do not know. If this is something I can check on my end or something,
pls let me know. This is a new PC, and I did not change any UAC settings
on it. All default setting on windows 7.
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);
OK, Will do that, I need to muck around the perl code and find where to
do this. will let you know if it changes anything.
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 100.
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.
OK, will make an official report.
Also, where do have your latex2html from?
I have documented the latex2html installation on my page below, so I
suppose anyone can reproduce what I did easily (if they have windows 7,
64 bit OS, which I do not know if it is releated or not). Please see
below for the steps:
http://12000.org/my_notes/l2hwin/index.htm
--Nasser
--
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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/6/2010 8:32 PM, Reini Urban wrote:
=
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. #
Hello;
I added the sleep above, made no difference: (also tried with sleep(.5),
same, the error still there:
entering L2hos::Unix::syswait
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) {
268: sleep(0.2);
269: $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 100.
275: unless(exec($cmd)) {
0 [main] perl 4796 C:\cygwin\bin\perl.exe: *** fatal error -
Internal error: TP_NUM_W_BUFS too small.
270: carp Debug (syswait): Finished child process:
#$child_pid\n
271: if($Verbose);
272: $child_pid = 0;
273: return($?);
exited L2hos::Unix::syswait
==
--Nasser
--
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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On Jun 3 12:02, Nasser M. Abbasi wrote: On 6/3/2010 12:43 AM, n...@12000.org wrote: Hello, SUMMARY: I installed cygwin 1.7.5 on windows 7 (64 bit OS), and when I run some command which uses perl, I get the following error: 0 [main] perl 2528 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Update: I deleted c:\cygwin, and did a complete new install. Problem is still there: Generating postscript images using dvips ... This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2010.06.03:1155' - /cygdrive/G/LATEX/TMP/l2h472/image (- /cygdrive/G/LATEX/TMP/l2h472/image001) tex.proalt-rule.protexps.pro special.procolor.procmr7.pfbcmex10.pfbcmsy10.pfbcmr10.pfb cmmi10.pfb[1] (- /cygdrive/G/LATEX/TMP/l2h472/image002) tex.pro alt-rule.protexps.prospecial.procolor.procmr7.pfbcmex10.pfb cmsy10.pfbcmr10.pfbcmmi10.pfb[2] Converting image #2 0 [main] perl 4752 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image 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 -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
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 I tried doing strace -o logfile make test but the output was too large, and the make seems to become slower and slower, after the file got to be over 2 GB and still growing, I killed everything. So, I tried this next: edited the Makefile and added -d to the perl command in the Makefile, then typed $ export PERLDB_OPTS=NonStop frame=2 make test This below is a small part of the screen output around the perl crash, may be this will help? again, i am not familar with perl or debugging it, but will be happy to help, if you have some specific instructions I can try. screen output= entering L2hos::Unix::syswait This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2010.06.04:0234' - /cygdrive/G/LATEX/TMP/l2h2264/image (- /cygdrive/G/LATEX/TMP/l2h2264/image001) tex.protexps.prospecial.pro color.procmr8.pfbcmsy10.pfbcmr12.pfbcmmi12.pfb[1] (- /cygdrive/G/LATEX/TMP/l2h2264/image002) tex.protexps.prospecial.pro color.procmex10.pfbcmr8.pfbcmsy10.pfbcmr12.pfbcmmi12.pfb[2] exited L2hos::Unix::syswait entering L2hos::Unix::Rename exited L2hos::Unix::Rename entering L2hos::Unix::Rename exited L2hos::Unix::Rename entering L2hos::Unix::Unlink exited L2hos::Unix::Unlink entering main::extract_image entering NDBM_File::FETCH exited NDBM_File::FETCH entering NDBM_File::FETCH exited NDBM_File::FETCH entering L2hos::Unix::Unlink exited L2hos::Unix::Unlink Converting image #2 entering L2hos::Unix::syswait 0 [main] perl 1312 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. exited L2hos::Unix::syswait Error while converting image entering main::write_warnings exited main::write_warnings entering main::embed_image entering main::get_image_size exited main::get_image_size === screen output --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
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
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.
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) {
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 100.
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
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
Hello, SUMMARY: I installed cygwin 1.7.5 on windows 7 (64 bit OS), and when I run some command which uses perl, I get the following error: 0 [main] perl 2528 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. DETAILS: I installed cygwin, all of it on windows 7, 64 bit os. All went ok. Then I installed latex2html, and I am trying to use latex2html under cygwin, which uses perl. (latex2hml is a PERL script) When I run latex2html command on some latex file, I get many of the above errors each time perl is called: $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin $ cygcheck -c | grep perl perl5.10.1-3OK perl-Error 0.17016-1 OK perl-ExtUtils-Depends 0.302-1 OK perl-ExtUtils-PkgConfig 1.12-1 OK perl-Graphics-Magick1.3.7-2 OK perl-Image-Magick 6.4.0.6-2 OK perl-libwin32 0.28-3 OK perl-Locale-gettext 1.05-11 OK perl-ming 0.4.3-1 Incomplete perl-SGMLSpm1.03ii-2OK perl-Tk 804.028-3 OK perl-Win32-GUI 1.06-3 OK perl-XML-Simple 2.18-10 OK perl_manpages 5.10.1-3OK postgresql-plperl 8.2.11-1OK subversion-perl 1.6.11-1OK $ $make test . Converting image #2 1 [main] perl 3104 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image I also was wondering, it it would be possible to a use windows perl.exe installation that I have from withing cygwin? thanks --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
Quoting n...@12000.org: Hello, SUMMARY: I installed cygwin 1.7.5 on windows 7 (64 bit OS), and when I run some command which uses perl, I get the following error: 0 [main] perl 2528 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. SNIP fyi; I found this below, which might be related? http://readlist.com/lists/cygwin.com/cygwin/6/34365.html may be this will help some cygwin expert. Without perl working for me under cygwin, I am dead in the water now. --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 3:43 AM, n...@12000.org wrote: perl-ming 0.4.3-1 Incomplete That's not right. I'd suggest reinstalling perl-ming. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 8:08 AM, Larry Hall (Cygwin) wrote: On 6/3/2010 3:43 AM, n...@12000.org wrote: perl-ming 0.4.3-1 Incomplete That's not right. I'd suggest reinstalling perl-ming. I did the following: 1. reinstalled. 2. tried different source, downloaded, reinstalled I still get the same thing, that perl-ming is Incomplete. Anything else I can try? or any other information I can provide to help resolve this? When I first installed cygwin, I installed everything. I did this from http://mirrors.kernel.org initially, and now from some other cygwin source. Is someone else getting this Incomplete on perl-ming? thanks --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 12:32 PM, Nasser M. Abbasi wrote: On 6/3/2010 8:08 AM, Larry Hall (Cygwin) wrote: On 6/3/2010 3:43 AM, n...@12000.org wrote: perl-ming 0.4.3-1 Incomplete That's not right. I'd suggest reinstalling perl-ming. I did the following: 1. reinstalled. 2. tried different source, downloaded, reinstalled I still get the same thing, that perl-ming is Incomplete. Anything else I can try? or any other information I can provide to help resolve this? When I first installed cygwin, I installed everything. I did this from http://mirrors.kernel.org initially, and now from some other cygwin source. Is someone else getting this Incomplete on perl-ming? Yeah, I am. Perhaps it's just a red-herring. A quick check doesn't indicate anything is missing. I'd say just ignore it or uninstall it (unless you need SWF support). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
Larry Hall (Cygwin) wrote: On 6/3/2010 3:43 AM, n...@12000.org wrote: perl-ming 0.4.3-1 Incomplete That's not right. I'd suggest reinstalling perl-ming. Perhaps it has something to do with the colons in the manpage filenames? Yaakov -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 1:40 PM, Yaakov (Cygwin/X) wrote: Larry Hall (Cygwin) wrote: On 6/3/2010 3:43 AM, n...@12000.org wrote: perl-ming 0.4.3-1 Incomplete That's not right. I'd suggest reinstalling perl-ming. Perhaps it has something to do with the colons in the manpage filenames? That's possible. I haven't dug into 'cygcheck' source to look for the real answer. I only did a quick verify with: zcat /etc/setup/perl-ming.lst.gz | xargs ls -1 I did this from '/'. But since 'cygcheck' doesn't use Cygwin, there could be file name issues there. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 12:43 AM, n...@12000.org wrote: Hello, SUMMARY: I installed cygwin 1.7.5 on windows 7 (64 bit OS), and when I run some command which uses perl, I get the following error: 0 [main] perl 2528 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Update: I deleted c:\cygwin, and did a complete new install. Problem is still there: Generating postscript images using dvips ... This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2010.06.03:1155' - /cygdrive/G/LATEX/TMP/l2h472/image (- /cygdrive/G/LATEX/TMP/l2h472/image001) tex.proalt-rule.protexps.pro special.procolor.procmr7.pfbcmex10.pfbcmsy10.pfbcmr10.pfb cmmi10.pfb[1] (- /cygdrive/G/LATEX/TMP/l2h472/image002) tex.pro alt-rule.protexps.prospecial.procolor.procmr7.pfbcmex10.pfb cmsy10.pfbcmr10.pfbcmmi10.pfb[2] Converting image #2 0 [main] perl 4752 C:\cygwin\bin\perl.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small. Error while converting image 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. I'll send email to the latex2html mailing list to see if someone there knows anything. If anyone has any suggestion to try, I'll do it. I am at a loss now what to do. I'll try to use my windows perl from inside cygwin, but I was trying to avoid doing this due to many problems this can cause. Should I try building cygwin from sources on my PC? I tried running perl on some small script (hello world) and no problem, it works ok. $ perl -v This is perl, v5.10.1 (*) built for i686-cygwin-thread-multi-64int (with 12 registered patches, see perl -V for more detail) Copyright 1987-2009, Larry Wall $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 Cygwin $ --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 3:02 PM, Nasser M. Abbasi wrote: Should I try building cygwin from sources on my PC? Debugging it further would certainly be helpful. But if you don't actually want to build Cygwin from source, you can always use a recent snapshot with its source and debugging information as a shortcut. http://cygwin.com/snapshots/ -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 12:17 PM, Larry Hall (Cygwin) wrote: On 6/3/2010 3:02 PM, Nasser M. Abbasi wrote: Should I try building cygwin from sources on my PC? Debugging it further would certainly be helpful. But if you don't actually want to build Cygwin from source, you can always use a recent snapshot with its source and debugging information as a shortcut. http://cygwin.com/snapshots/ I did. I installed the latest snapshot from http://cygwin.com/snapshots/ cygwin-inst-20100602.tar.bz2 Followed instructions on http://www.cygwin.com/faq/faq.setup.html#faq.setup.snapshots started the cygwin shell again: $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5s(0.227/5/3) 20100602 12:11:53 i686 Cygwin Run make again, and I still get the same perl error. I do not know perl much at all. I wonder if there is a way to turn some perl global debugging somehow, may be if there is a perl message files, that will help find the problem? I need to google this. I am not running perl directly, it is being called from within the latex2html makefile. Next step for me I suppose is to see if I can use my windows perl installation (Active Perl 5.1) from inside cygwin instead of the cygwin perl. --Nasser -- 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
Re: cygwin 1.7.5, perl *** fatal error TP_NUM_W_BUFS too smal
On 6/3/2010 4:19 PM, Nasser M. Abbasi wrote: On 6/3/2010 12:17 PM, Larry Hall (Cygwin) wrote: On 6/3/2010 3:02 PM, Nasser M. Abbasi wrote: Should I try building cygwin from sources on my PC? Debugging it further would certainly be helpful. But if you don't actually want to build Cygwin from source, you can always use a recent snapshot with its source and debugging information as a shortcut. http://cygwin.com/snapshots/ I did. I installed the latest snapshot from http://cygwin.com/snapshots/ cygwin-inst-20100602.tar.bz2 Followed instructions on http://www.cygwin.com/faq/faq.setup.html#faq.setup.snapshots started the cygwin shell again: $ uname -a CYGWIN_NT-6.1-WOW64 me-PC 1.7.5s(0.227/5/3) 20100602 12:11:53 i686 Cygwin Run make again, and I still get the same perl error. I do not know perl much at all. I wonder if there is a way to turn some perl global debugging somehow, may be if there is a perl message files, that will help find the problem? I need to google this. Actually, my thought was to install the complete source and debugging symbols from http://cygwin.com/snapshots/ too so that you could set a breakpoint in the code that issues the error and get a better understanding as to why. For that, you don't need to know or even debug Perl (one would hope ;-) ). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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
