2006/8/3, Igor Peshansky <[EMAIL PROTECTED]>:
On Wed, 2 Aug 2006, Igor Peshansky wrote:
> $ perl -e 'use Win32::GUI qw(MessageBox); MessageBox(0, "message", "title",
64);'
> Can't load '/usr/lib/perl5/site_perl/5.8/cygwin/auto/Win32/GUI/GUI.dll' for
module Win32::GUI: No such file or directory at
/usr/lib/perl5/5.8/cygwin/DynaLoader.pm line 230.
> at -e line 1
> Compilation failed in require at -e line 1.
> BEGIN failed--compilation aborted at -e line 1.
>
> At this point the perl.exe process started consuming 100% of the CPU and
> allocating memory like crazy. I let it get to 1.2G before killing it
> (took about 35 minutes). It did react to a Ctrl-C in the parent bash
> window.
>
> I wasn't able to open another Cygwin window and attach to the hanging
> process with strace, because my system slowed down to a crawl and stopped
> responding to most window messages. Perhaps I'll repeat the experiment
> someday.
Actually, in a typical "D'oh!" moment I realized that I can simply start
the perl process under strace -- if I kill it early enough, it doesn't
affect my system too much. The strace wasn't very illuminating as to the
cause of not finding the DLL (Windows error 126), but it did have a weird
sequence of mmap()/munmap() that seems to be the cause of 100% CPU and the
virtual memory allocation.
Interesting. Does it go away a rebaseall?
If you're interested in tracking this down further, I can send you the
strace off-list.
If it doesn't go away, yes please. Something for p5p maybe
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
http://spacemovie.mur.at/ http://helsinki.at/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
