X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=nu
	BTrYb6g7mGhA/J2vyiLMg0bQ27bYEMMNM/Rf+djUM6DYjlUzQoSmTqHopM6OYWfi
	w7I5j/NH83mQvrGFzvVGJwTyepPEa0MvJJz2LqKPmX2jnBAgY3+2jj/wwftsKmiD
	qhLcsQ9+m05xYAoKKgbP+GZQdv4RQ0SpEpLUITPzU=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=cjFdmYt0
	ZzCzuqzthcj3UnqWnmk=; b=euiq2aFHZAcLbAiNOCQ1LsnWIsRB+6a44r2VRRnR
	+5Sk4LW4DSiWvY7D19wepnNlb52oWZIvyZQ8wQvyW1a0wy3JeJbP/KGk3DEYetEu
	Pzdc0DXOvz6/rmf+FoDsh+MjHgbQTi4d43qEsJBsIyvUgTwgKj5WO/WAZGZj00FV
	w74=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
X-Spam-SWARE-Status:	No, score=-3.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
MIME-Version:	1.0
X-Received:	by 10.224.49.130 with SMTP id v2mr19692399qaf.75.1377204411220; Thu, 22 Aug 2013 13:46:51 -0700 (PDT)
In-Reply-To:	<20130822171419.GQ2562@calimero.vinschen.de>
References:	<52162CA9 DOT 9080002 AT etr-usa DOT com> <20130822171419 DOT GQ2562 AT calimero DOT vinschen DOT de>
Date:	Thu, 22 Aug 2013 16:46:51 -0400
Message-ID:	<CA+sc5mnedD0hOfzwTWYzy0QVhKC9gg-C68Nxfska-HG0HFOpLQ@mail.gmail.com>
Subject:	Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?
From:	Earnie Boyd <earnie AT users DOT sourceforge DOT net>
To:	Andrey Repin <cygwin AT cygwin DOT com>

On Thu, Aug 22, 2013 at 1:14 PM, Corinna Vinschen wrote:
>
> When execveing a Cygwin process, a lot of data is submitted via shared
> memory, via data copying, and via a special parameter to the
> CreateProcess call with the mysterious name "lpReserved2".
>
> One problem is the differences in basic datatypes, which results in
> incompatible datastructures between 32 and 64 bit.  While this could be
> worked around, this doesn't help for the shared memory stuff, which
> depends on the installation path of the cygwin DLL.  The Cygwin DLL in
> C:\cygwin1 would use a different name for the shared mem regions than
> the Cygwin DLL installed into C:\cygwin2, independent of the target
> architecture.  This is by design since Cygwin 1.7.  One effect:  No tty
> sharing.
>

Since you know that the DLL regions are different what about execing
the process as if it were a windows native process?  I know you loose
the ability to do the parent/child relationship but it isn't any worse
than spawning a native process.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

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

- Raw text -