This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin 1.78 errors when invoking terminator (*** fatal error - MapViewOfFileEx '(null)'(0x708), Win32 error 6. Terminating.)
On Thu, Mar 3, 2011 at 02:43, Corinna Vinschen wrote:
> On Mar ?2 18:01, Kenneth Wolcott wrote:
>> ? 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 (firstname.lastname@example.org).
>> ? 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).
>> 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));
>> ?# ifdef __GNUC__
>> -int????? _EXFUN(strerror_r,(int, char *, size_t)) __asm__ ("__xpg_strerror_r");
>> +int????? _EXFUN(strerror_r,(int, char *, size_t)) __asm__
>> ?# 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,
The problem seems to be fixed now (after a recent update).
CYGWIN_NT-5.1 KWOLCOTT-T61 1.7.8(0.236/5/3) 2011-03-01 09:36 i686 Cygwin
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple