X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Thu, 3 Mar 2011 11:43:19 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.78 errors when invoking terminator (*** fatal error - MapViewOfFileEx '(null)'(0x708), Win32 error 6. Terminating.)
Message-ID: <20110303104319.GB16272@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <AANLkTimV5xz+Ac+VFN8NwEsnTZFq8OD0L3ngPKwUW0MU AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <AANLkTimV5xz+Ac+VFN8NwEsnTZFq8OD0L3ngPKwUW0MU@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

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

-- 
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