Mail Archives: cygwin/2002/02/06/21:55:12
Hi,
I observed cygwin getting into a bad state after a
memory-allocation failure, from which I only can
recover by terminating all cygwin processes to unload
the cygwin1.dll.
I run a perl script that gradually allocates memory
until the memory limit of 256 MB (default) is reached.
Perl, as expected, terminates with "Out of Memory!"
However, _after_ the script terminates,
subsequently executed cygwin programs have a problem:
- a simple "ls" gives
Segmentation fault (core dumped)
% ls -l
... (works correctly)
% ./test.pl <-- script to reach mem limit
Out of memory!
% ls -l
Segmentation fault (core dumped)
%
- trying to open another rxvt window (while the shell in which
the script terminated is still open) shows the msg
handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
To recover, I need to exit the shell in which the script
terminated first, such that all cygwin processes are gone
(and cygwin1.dll gets unloaded, I guess).
Thanks,
Frank
Version info:
- This is perl, version 5.005_03 built for cygwin32
- WinNT Ver 5.0 build 2195 Service Pack 2
- Cygwin DLL version info:
dll major: 1003
dll minor: 2
dll epoch: 19
dll bad signal mask: 19005
dll old termios: 5
dll malloc env: 28
api major: 0
api minor: 39
shared data: 3
dll identifier: cygwin1
mount registry: 2
cygnus registry name: Cygnus Solutions
cygwin registry name: Cygwin
program options name: Program Options
cygwin mount registry name: mounts v2
cygdrive flags: cygdrive flags
cygdrive prefix: cygdrive prefix
cygdrive default prefix:
build date: Sun May 20 23:28:17 EDT 2001
shared id: cygwin1S3
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -