This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cygwin-1.7.10-1 fork - address space needed by ... already in use
- From: Denis Excoffier <cygwin at Denis-Excoffier dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 5 Mar 2012 08:09:03 +0100
- Subject: Re: cygwin-1.7.10-1 fork - address space needed by ... already in use
- References: <33279157.post@talk.nabble.com> <20120207154359.GA2952@qp9482> <20120207161428.GB12159@calimero.vinschen.de> <4F31559B.6060600@cs.utoronto.ca> <B0ED7173-1AC3-4B4E-8B79-3A9B22652684@Denis-Excoffier.org> <20120208090824.GA1724@qp9482> <20120208092711.GF25129@calimero.vinschen.de> <20120208102235.GA2796@qp9482> <20120304172210.GI18852@calimero.vinschen.de>
On Sun, Mar 04, 2012 at 06:22:10PM +0100, Corinna Vinschen wrote:
>> On Feb 8 11:22, Denis Excoffier wrote:
>> > On Wed, Feb 08, 2012 at 10:27:11AM +0100, Corinna Vinschen wrote:
>> > >> On Feb 8 10:08, Denis Excoffier wrote:
>> > >> > Result is:
>> > >> >
>> > >> > 1 [main] gcc-4 4084 dll_list::reserve_space: address space needed by 'cygiconv-2.dll' (0x674C0000 with type 1=DLL_LINK) is perhaps already occupied
>> > >> > 1720 [main] gcc-4 4084 dll_list::reserve_space: address space needed by 'cygintl-8.dll' (0x6F5C0000 with type 1=DLL_LINK) is perhaps already occupied
>> > >> > 2085 [main] gcc-4 4084 dll_list::reserve_space: address space needed by 'cygiconv-2.dll' (0x674C0000 with type 2=DLL_LOAD) is perhaps already occupied
>> > >> > 2440 [main] gcc-4 4084 dll_list::reserve_space: address space needed by 'cygintl-8.dll' (0x6F5C0000 with type 2=DLL_LOAD) is perhaps already occupied
>>
>> Denis, can you please give the latest snapshot DLL a try in all
>> circumstances in which you saw the above kind of fork problems in
>> 1.7.10? I applied a patch which should now work out the differences
>> between linked and loaded DLLs better than before.
>>
% uname -a
CYGWIN_NT-5.1 edited 1.7.12s(0.260/5/3) 20120304 17:49:39 i686 Cygwin
%
I am now unable to report any problem of that sort. I have compiled the
cygwin1.dll, the new gcc-4.7.0-rc-20120302, and several other
packages with no occurrence of such a message.
I've only to report that i observe some time to time the "something
failed for pid" message (see several instances below). "Win32 Error 5"
is ERROR_ACCESS_DENIED i suppose (in winerrors.h). I don't know
what we are expected to do with these. In addition, they do not seem
to hurt much.
Also i've to say that i've installed the CYGWIN=detect_bloda
and nothing has shown up (still).
Regards,
Denis Excoffier.
947 [main] sh 660! _pinfo::dup_proc_pipe: something failed for pid 0: res 660, hProcess 0x6C8, wr_proc_pipe 0x758 vs. 0x758, Win32 error 5
2 [main] sh 3360! _pinfo::dup_proc_pipe: something failed for pid 0: res 3360, hProcess 0x6BC, wr_proc_pipe 0x758 vs. 0x758, Win32 error 5
1345 [main] sh 3772! _pinfo::dup_proc_pipe: something failed for pid 0: res 3772, hProcess 0x6CC, wr_proc_pipe 0x758 vs. 0x758, Win32 error 5
2 [main] sh 792! _pinfo::dup_proc_pipe: something failed for pid 0: res 792, hProcess 0x6D0, wr_proc_pipe 0x75C vs. 0x75C, Win32 error 5
1 [main] sh 3328! _pinfo::dup_proc_pipe: something failed for pid 0: res 3328, hProcess 0x6BC, wr_proc_pipe 0x758 vs. 0x758, Win32 error 5
1 [main] sh 1980! _pinfo::dup_proc_pipe: something failed for pid 0: res 1980, hProcess 0x6BC, wr_proc_pipe 0x74C vs. 0x74C, Win32 error 5
1 [main] sh 628! _pinfo::dup_proc_pipe: something failed for pid 0: res 628, hProcess 0x6BC, wr_proc_pipe 0x758 vs. 0x758, Win32 error 5
1 [main] sh 856! _pinfo::dup_proc_pipe: something failed for pid 0: res 856, hProcess 0x6BC, wr_proc_pipe 0x758 vs. 0x758, Win32 error 5
1 [main] tcsh 3300! _pinfo::dup_proc_pipe: something failed for pid 0: res 3300, hProcess 0x6F0, wr_proc_pipe 0x768 vs. 0x768, Win32 error 5
>>
>> Thanks,
>> 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
--
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