X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <041701c83682$340bb510$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <14297841 DOT post AT talk DOT nabble DOT com> <14298291 DOT post AT talk DOT nabble DOT com> <14300048 DOT post AT talk DOT nabble DOT com> <14301296 DOT post AT talk DOT nabble DOT com> Subject: RE: Not yet supported (was: emacs shell) Date: Wed, 12 Dec 2007 18:52:27 -0000 Message-ID: <003001c83cf0$26a58b20$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <14301296.post@talk.nabble.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 12 December 2007 18:40, Marc Girod wrote: >> And the error in the terminal from where emacs was started is (several >> times each code, as if at random, with different address ranges): >> >> 379530601 [main] emacs 4964 child_copy: linked dll data write copy failed, >> 0x33B000..0x33B440, done 0, windows pid 4080, Win32 error 487 >> 570693374 [main] emacs 4964 child_copy: linked dll data write copy failed, >> 0x940000..0x940240, done 0, windows pid 4080, Win32 error 998 >> > > OK. I get now the same kind of errors again with startx: > > 326 [main] xterm 4680 child_copy: linked dll data write copy failed, > 0x869000..0x86CF40, done 0, windows pid 5416, Win32 error 87 > xterm: Error 29, errno 11: Resource temporarily unavailable > Reason: spawn: fork() failed > xinit: Resource temporarily unavailable (errno 11): can't send HUP to > process group 4680 > > ...and I found such hits in older messages in the archive, with other > variants of Windows, in conjunction to inconsistent versions of cygwin1.dll. That's one thing that can cause it. Another cause is interference from system-call-hooking software such as anti-virus and firewalls. What the error message is trying to tell you is that during the fork operation, it has been unable to duplicate an area of memory from the parent process into the child process. Since it's a requirement that fork() create child processes identically laid out to their parents, this is a fatal situation. > I checked there is no such problem now. Good. The next things to try would be running a rebaseall[*], and checking the BLODA[**]. > But running 'cygcheck -s', I got into: > > Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Yes, Vista isn't well supported; not a lot of the list members even have it! cheers, DaveK [*] - less -c /usr/share/doc/Cygwin/rebase-2.4.3.README [**] - http://cygwin.com/ml/cygwin-talk/2007-q4/msg00026.html -- Can't think of a witty .sigline today.... -- 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/