X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=4.0 required=5.0 tests=AWL,BAYES_00,BOTNET,RCVD_IN_DNSWL_NONE,URIBL_RHS_DOB X-Spam-Check-By: sourceware.org Message-id: <4D8BC5BE.2070100@cygwin.com> Date: Thu, 24 Mar 2011 18:29:18 -0400 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin 1.78 errors when invoking terminator (*** fatal error - MapViewOfFileEx '(null)'(0x708), Win32 error 6. Terminating.) References: <20110303104319 DOT GB16272 AT calimero DOT vinschen DOT de> In-reply-to: Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 3/24/2011 6:11 PM, Kenneth Wolcott wrote: > On Thu, Mar 3, 2011 at 02:43, Corinna Vinschen wrote: >> On Mar 2 18:01, Kenneth Wolcott wrote: >>> Hi; >>> >>> I get the following error output when opening a terminator (enclosed >>> at bottom of the email). >>> >>> This is the jessies.org terminator, not the gnome terminator. >>> >>> Now I don't get the following when I open a cygwin prompt. >>> >>> So I thought it might be a terminator thing. >>> >>> I had just updated to 1.78 of Cygwin. >>> >>> So updated to the most current version of terminator. >>> >>> Same problem. >>> >>> So I posted to the terminator email list (terminator-users AT googlegroups DOT com). >>> >>> The terminator developer/maintainer was able to reproduce the >>> problem and thinks that the error is within cygwin and suggests this >>> patch (between the splat-asterisk lines). >>> >>> Thanks, >>> Ken Wolcott >>> >>> *&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*&*& >>> >>> I wouldn't like to claim this is the right fix but it lets that >>> trivial example link: >>> >>> $ gcc strerror.c >>> >>> $ diff -u /usr/include/string.h.orig /usr/include/string.h >>> --- /usr/include/string.h.orig 2011-03-02 10:49:29.510836800 -0800 >>> +++ /usr/include/string.h 2011-03-02 10:50:04.324450800 -0800 >>> @@ -74,7 +74,7 @@ >>> char *_EXFUN(strerror_r,(int, char *, size_t)); >>> #else >>> # ifdef __GNUC__ >>> -int _EXFUN(strerror_r,(int, char *, size_t)) __asm__ ("__xpg_strerror_r"); >>> +int _EXFUN(strerror_r,(int, char *, size_t)) __asm__ >>> ("___xpg_strerror_r"); >>> # else >>> int _EXFUN(__xpg_strerror_r,(int, char *, size_t)); >>> # define strerror_r __xpg_strerror_r >>> $ >> >> Thanks for the report. I just fixed that in CVS. The problem here >> is that we have to take several targets into account, some of them >> using a labe lprefix, some of them not. I applied a patch which >> does that: >> >> int _EXFUN(strerror_r,(int, char *, size_t)) __asm__ (__ASMNAME ("__xpg_strerror_r")); >> >> The __ASMNAME macro is now defined in cdefs.h. I tested to build >> a testcase which calls the POSIX version of strerror_r and it now >> works fine. Well, there was a small bug in __xpg_strerror_r, too, >> but that should be fixed in CVS as well. I'll create a new developer >> snapshot later today. >> >> >> Thanks again, >> Corinna > > > Hi Corinna; > > The problem seems to be fixed now (after a recent update). > > uname.exe -a > CYGWIN_NT-5.1 KWOLCOTT-T61 1.7.8(0.236/5/3) 2011-03-01 09:36 i686 Cygwin Since Corinna replied on 3/3 and your Cygwin DLL version was built on 3/1, I think it's fair to assume that you don't have the change she was talking about. But you can get an updated Cygwin DLL with the change by visiting . -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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