Error when Perl calling shell scipt using Cygwin c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487
http://old.nabble.com/file/p31714033/cygcheck.out cygcheck.out Hi, I have a Windows machine and I have Cygwin installed. I have a Perl script which calls a shell script using Cygwin. I am getting the following message while running the Perl script: 5 [main] sh 6632 c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x8F, top 0x94, reserve_size 323584, allocsize 327680, page_const 40966 [main] sh 6232 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] sh 3784 c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x8F, top 0x94, reserve_size 323584, allocsize 327680, page_const 40963016351 [main] sh 6232 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] sh 6156 c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x8F, top 0x94, reserve_size 323584, allocsize 327680, page_const 40966916676 [main] sh 6232 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] sh 7668 c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x8F, top 0x94, reserve_size 323584, allocsize 327680, page_const 409612806997 [main] sh 6232 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 6 [main] sh 3132 c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x8F, top 0x94, reserve_size 323584, allocsize 327680, page_const 409622683401 [main] sh 6232 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 c:\myscript.sh: fork: Resource temporarily unavailable I searched various links, and tried out different suggestions that worked for others but to no avail. Few things that I tried was: -- 1. Disabled SEP (Symantec Endpoint Protection) 2. Turned off DEP (Data Execution Prevention) for Cygwin’s sh.exe 3. Modified numbers (,,) present in Windows key value at the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\ 4. Ran rebaseall in ash.exe -- The strange thing is that if I directly call the shell script using Cygwin, it works fine. c:\cygwin\bin\sh.exe c:\myscript.sh cygcheck -V gave the following output: -- $ cygcheck -V cygcheck version 1.123 System Checker for Cygwin Copyright (C) 1998 - 2008 Red Hat, Inc. Compiled on Apr 12 2010 -- I think this version of Cygwin is quite old so I am planning to install a separate instance (latest) but what concerns me is that since the shell script works fine without using Perl, and fails when using Perl, there seems to be some issue either with -- 1. Perl itself 2. compatibility between Perl Cygwin versions -- I have also attached the output of ‘cygcheck -s -v –r’. However, I have modified/removed few sensitive info. Can anyone provide some help to get this thing working? Thanks, Gaurav -- View this message in context: http://old.nabble.com/Error-when-Perl-calling-shell-scipt-using-Cygwin-%3E%3E%3E-c%3A%5Ccygwin%5Cbin%5Csh.exe%3A-***-fatal-error---couldn%27t-allocate-heap%2C-Win32-error-487-tp31714033p31714033.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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: Does Latex/Tex install? Does Latex/Tex work? How do you get it installed? How do you get it to work?
I have installed and use 'texlive 2010', as is, on cygwin with no problem. No need for MikTeX or Windows interfaces. Using TexLive also eases things since it uses normal posix pathnames. Regards, Wynfield -- 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: Does Latex/Tex install? Does Latex/Tex work? How do you get it installed? How do you get it to work?
On Fri, May 27, 2011 at 12:39 AM, Charles Wilson wrote: On 5/26/2011 4:47 PM, marco atzeri wrote: On Thu, May 26, 2011 at 10:33 PM, Dima Pasechnik wrote: tetex is dead and buried. Indeed, http://www.tug.org/tetex/ says: --- De-support notice I (Thomas Esser) have decided not to make new releases of teTeX any more (May 2006). --- In fact, newer (la)tex packages tend not to work with tetex. Perhaps it is time for cygwin to switch to Tex Live. feel free to volunteer for packing it. Well, hold on there, cowboy. Jan Nieuwenhuizen is listed as the teTeX maintainer for cygwin; I think to proper course is to ask Jan to update/switch cygwin's TeX system to TeX Live, and make the case for why it should happen. Tex Live will be another package, so it could have another maintainer. No one will complain about additional volunteers. ;-) TexLive has a peculiar installation, so making a cygwin package is not a trivial task. I think teTeX has been dead upstream for five years is a pretty good argument, actually. using a typical CGF's answer: http://cygwin.com/acronyms/#SHTDI 'Course, we haven't heard from Jan since last Novemeber http://cygwin.com/ml/cygwin/2010-11/msg00422.html so... Jan? You still there? following gmane, he seems busy with lilypond and mingw -- 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
File Name Case Sensitivity Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
You got that wrong. The CYGWIN=glob:... option only affects how globbing is performed on the command line arguments if the Cygwin process has been started from a native Windows process. Full stop. I acknowledged *my* MISTAKE. I do so again. Now, actual filename case sensitivity is an entirely different issue. This is handled by a registry setting, the ability of the underlying filesystems to handle filenames case sesitive, and the settings of the Cygwin mount point: http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive http://cygwin.com/cygwin-ug-net/using.html#mount-table I acknowledged this point as well in my initial post, and why I reject it. The point remains: Globbing is case sensitive while full command name invocation/full filename use is not. And, you may never have been confused by that, but I maintain it's very confusing. I'm not asking that it be fixed, I'm asking that it be carefully documented, and I'm not asking anyone but me to do it. If it is so documented, I missed it. And, I read and reread that part of the manual before posting both times. I offered an example session transcript that made that perfectly clear, and I am willing to write that up however you want it. Thus far, you've made clear you don't want it. No further replies will be required if my last read is correct. -- 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: File Name Case Sensitivity Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
On May 27 11:53, Lee D. Rothstein wrote: You got that wrong. The CYGWIN=glob:... option only affects how globbing is performed on the command line arguments if the Cygwin process has been started from a native Windows process. Full stop. I acknowledged *my* MISTAKE. I do so again. So actually I got it wrong. The point remains: Globbing is case sensitive while full command name invocation/full filename use is not. And, you may never have been confused by that, but I maintain it's very confusing. I'm not asking that it be fixed, I'm asking that it be carefully documented, and I'm not asking anyone but me to do it. If it is so documented, I missed it. And, I read and reread that part of the manual before posting both times. If anybody says our documentation is lacking, I'm the last to deny it. If you feel up to the task, patches to the documentation are more than welcome. 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: File Name Case Sensitivity Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
* Lee D. Rothstein (Fri, 27 May 2011 11:53:16 -0400) Globbing is case sensitive while full command name invocation/full filename use is not. And, you may never have been confused by that, but I maintain it's very confusing. This has nothing to do with Cygwin. You are (still[1]) confusing Cygwin and your shell. You would hugely benefit from gaining some basic knowledge about the tools you've been using since 1979. Your transcript was done in a shell called bash. Globbing in bash is - by default - case sensitive. If you want to change that, read the man page and then set option nocaseglob (shopt -s nocaseglob). Thorsten [1] http://www.cygwin.com/ml/cygwin/2003-02/msg01005.html -- 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: File Name Case Sensitivity Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
On Fri, May 27, 2011 at 12:38, Thorsten Kampe thors...@thorstenkampe.de wrote: This has nothing to do with Cygwin. You are (still[1]) confusing Cygwin and your shell. You would hugely benefit from gaining some basic knowledge about the tools you've been using since 1979. Your transcript was done in a shell called bash. Globbing in bash is - by default - case sensitive. If you want to change that, read the man page and then set option nocaseglob (shopt -s nocaseglob). The globbing is not where the confusion lies. This globbing: $ ls xwin* ls: cannot access xwin*: No such file or directory works as expected and did not confuse anybody. Here's what confused the OP: $ ls xwin xwin $ ls xwIN xwIN This is unquestionably a normal, Cygwin specific condition, caused by the semantics of the underlying NTFS, but very confusing to someone whose experience is with UNIX. This note: http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive warns that you cannot have two filenames in the same directory that differ only by case, because of NTFS semantics. It could be improved to warn that because of NTFS semantics there are also filenames which exist but which Cygwin's readdir() does not return, and which therefore are truly hidden -- will never show up in directory listings or globs. I think this is what the OP was volunteering to do. Cheers, MetaEd -- 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: File Name Case Sensitivity Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
* Edward McGuire (Fri, 27 May 2011 16:36:06 -0500) The globbing is not where the confusion lies. This globbing: $ ls xwin* ls: cannot access xwin*: No such file or directory works as expected and did not confuse anybody. Lee begs to differ: Globbing is case sensitive [while ...]. And, you may never have been confused by that, but I maintain it's very confusing. Here's what confused the OP: $ ls xwin xwin $ ls xwIN xwIN Interesting that you know that this is what confused Lee - although he doesn't mention it all in his transcript (http://permalink.gmane.org/gmane.os.cygwin/126959). Thorsten -- 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: Can't talk to X server through ssh tunnel after ~ 18 minutes
I have a similar issue on Windows 7 64 bit. I don't even use SSH. I can just run an Xterm or other X app with display pointed directly to the IP (after doing proper xhost, etc), and the window will display (often I'll get crashes and stack traces a few times, then it will display). But then the windows will just vanish for no real reason. The X application will still be running on the remote box, but the window is no where to be found on the display. I typically kill off the xterm on the remote box and run it again. It's like the X server under windows is simply unmapping the window and it goes into never-never land. It happens fairly randomly to random clients running on the same or different hosts. One or two x-app windows will vanish from that host, while others are still running fine. Never happened to me under XP 32 bit. - Jim On 5/25/2011 10:43, Andrew DeFaria wrote: I ssh from my Cygwin box to a Linux machine (happens with Solaris machines too) and I can run X applications back to Cygwin/X without a problem. However, after a few minutes something happens to the tunnel and I can no longer put up any X windows: $ cat checks.sh #!/bin/bash while true; do date xclock sleep 2 killall xclock if [ $? != 0 ]; then echo Cannot talk to X Server anymore else sleep 60 fi done $ checkx.sh Tue May 24 09:48:43 PDT 2011 ./checkx.sh: line 12: 10927 Terminated xclock Tue May 24 09:49:45 PDT 2011 ./checkx.sh: line 12: 11393 Terminated xclock Tue May 24 09:50:47 PDT 2011 b./checkx.sh: line 12: 11592 Terminated xclock Tue May 24 09:51:49 PDT 2011 ./checkx.sh: line 12: 11782 Terminated xclock Tue May 24 09:52:51 PDT 2011 ./checkx.sh: line 12: 11977 Terminated xclock Tue May 24 09:53:53 PDT 2011 ./checkx.sh: line 12: 12161 Terminated xclock Tue May 24 09:54:55 PDT 2011 ./checkx.sh: line 12: 12345 Terminated xclock Tue May 24 09:55:57 PDT 2011 ./checkx.sh: line 12: 12534 Terminated xclock Tue May 24 09:56:59 PDT 2011 ./checkx.sh: line 12: 12723 Terminated xclock Tue May 24 09:58:01 PDT 2011 ./checkx.sh: line 12: 12912 Terminated xclock Tue May 24 09:59:03 PDT 2011 ./checkx.sh: line 12: 13142 Terminated xclock Tue May 24 10:00:05 PDT 2011 ./checkx.sh: line 12: 13345 Terminated xclock Tue May 24 10:01:07 PDT 2011 ./checkx.sh: line 12: 13578 Terminated xclock Tue May 24 10:02:09 PDT 2011 ./checkx.sh: line 12: 13843 Terminated xclock Tue May 24 10:03:11 PDT 2011 ./checkx.sh: line 12: 14074 Terminated xclock Tue May 24 10:04:13 PDT 2011 ./checkx.sh: line 12: 14260 Terminated xclock Tue May 24 10:05:16 PDT 2011 ./checkx.sh: line 12: 14455 Terminated xclock Tue May 24 10:06:18 PDT 2011 X connection to localhost:15.0 broken (explicit kill or server shutdown). xclock: no process killed Cannot talk to X Server anymore After this I cannot re-establish an X connection until I exit the ssh session and ssh back in again. Any ideas? (I'm gonna post this to both Cygwin and Cygwin-X as I'm not sure if this is a problem with ssh or a problem with X). smime.p7s Description: S/MIME Cryptographic Signature
src/winsup/cygwin ChangeLog shared.cc shared_i ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-05-27 06:11:05 Modified files: winsup/cygwin : ChangeLog shared.cc shared_info.h Log message: * shared.cc (offsets): Reorder so that console_state is lowest in memory. Explain why. (open_shared): Accommodate reordering of offsets array. * shared_info.h (shared_locations): Reorder SH_SHARED_CONSOLE after SH_MYSELF. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5374r2=1.5375 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/shared.cc.diff?cvsroot=srcr1=1.143r2=1.144 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/shared_info.h.diff?cvsroot=srcr1=1.90r2=1.91
