This is the mail archive of the
cygwin
mailing list for the Cygwin project.
extremely rarely fork errors: who occuppies the space?
- From: Heiko Elger <heiko_elger at arburg dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 6 Feb 2012 06:42:52 +0000 (UTC)
- Subject: extremely rarely fork errors: who occuppies the space?
Hello,
our current system is the following (cygwin installation is nearly up to date).
$ uname -a
CYGWIN_NT-6.1-WOW64 PCFX163 1.7.10s(0.259/5/3) 20120111 22:39:26 i686 Cygwin
some systems uses a newer snapshot:
uname -a
CYGWIN_NT-6.1-WOW64 PCFX061 1.7.10s(0.259/5/3) 20120202 16:59:00 i686 Cygwin
We've still some not reproduceable fork errors like the following
0 [main] sh 90024 child_info_fork::abort: address space needed
by 'cygiconv-2.dll' (0x6D0D0000) is already occupied
7 [main] sh 88036 child_info_fork::abort: address space needed
by 'cygiconv-2.dll' (0x6D0D0000) is already occupied
The error is extremely rarely - perhaps just once a day
Antivirus software is deinstalled, Windows defender is deactivated.
Rebaseall and peflagsall were running.
We have this error really not reproduceable on some compile machines.
These machines are running a perl script which polls a remote database for
running make jobs in parallel (-j flag) - that's all.
Normally all works fine - but sometimes we got these fork errors.
Is there an possibility to get more information who is occupying the address
space?
Perhaps I can instrument the cygwin1.dll to wait or do something special - so
I can use other tools i.e. sysinternals vmmap, process explorer ...
to have a look who is using this address space.
Perhaps a self build debug snapshot version with instrumented debug flags will
give me some hints?
Please - can anyone give me some hints.
Any help is welcome.
best regards
Heiko
--
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