X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_50,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,TW_CG X-Spam-Check-By: sourceware.org Message-ID: <50673248.5010505@x-ray.at> Date: Sat, 29 Sep 2012 12:39:20 -0500 From: Reini Urban User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: peflags makes perl not print to stdout References: In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit 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 On 09/27/2012 09:14 AM, Saurabh T wrote: > Hi, I asked this before and havent gotten a reply. Is there any other > information I can provide? This is currently quite a bummer for me. Any > help will be greatly appreciated. Thanks. > > ---------------------------- > > From: saurabh > To: cygwin > Subject: peflags makes perl not print to stdout > Date: Mon, 24 Sep 2012 17:29:42 +0000 > > I have been trying to get perl to use 2GB of memory (this > is on a 32 bit xp machine with 4 GB total memory). As per > http://cygwin.com/cygwin-ug-net/setup-maxmem.html I tried > peflags --cygwin-heap=2048 /usr/bin/perl > > However this causes perl to not write to screen. > On further investigation, I found the magic number to be 1040: > > $ peflags --cygwin-heap=1039 /usr/bin/perl > /usr/bin/perl: initial Cygwin heap size: 1039 (0x40f) MB > > $ perl -e 'print "Hello\n";' > Hello > > $ peflags --cygwin-heap=1040 /usr/bin/perl > /usr/bin/perl: initial Cygwin heap size: 1040 (0x410) MB > > $ perl -e 'print "Hello\n";' > > In other words, anything 1040 and above, perl stops writing to screen. > I have the latest cygwin (1.7.16) and perl (5.14.2). > Any idea what might be wrong? Thank you. Yes, strange. I'm not aware of any heap magic or IO limits within perl. (contrary to clisp or other binaries using a copying gc). It's pure malloc, and it memory and io is purely dynamic. If cgf has no idea either you need to ask that on p5p. -- 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