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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=LorlUcxE9Dz53vEm4y7HtzukiVvSPYEanIVk2Bqz9zw
	M74Pg3Ga53+1uQE9CWTZOCEflJ6k4YYSLu8IRCRTwBgF8Pk5yyuWUwBWPoxWKqvi
	hr5Uo+E3Xd6ZshCXbCZU25OTbNJXb6vRsWORkiS79VMFIep+vbEfagc8tGSrY24Y
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=eWIotho4B1d/ZA0Y6Kx7DKITCJs=; b=sR/LBikfMM0QAQuDN
	2np9W7qAYV6xUQMM4YL4eB0hctmoRs5r3lDG85OmXlin61K6gTNmxHLzkYBkJFiY
	Zn+ADSAohWR6GHDY3k4XGxT38Pjjm1f6QHgC5UbPAk+t/ZgKpparxPAZ7iM+7cI5
	+V1qXeBVyKgXrhHst8Z9Zaxjnk=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,UNSUBSCRIBE_BODY autolearn=no version=3.3.2
X-HELO: mail-wg0-f52.google.com
X-Received: by 10.195.13.102 with SMTP id ex6mr45615204wjd.48.1404158913533;        Mon, 30 Jun 2014 13:08:33 -0700 (PDT)
Message-ID: <53B1C3B8.9080401@gmail.com>
Date: Mon, 30 Jun 2014 22:08:24 +0200
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: can't share fifo between 32-bit and 64-bit Cygwins
References: <0D835E9B9CD07F40A48423F80D3B5A702E7D8967 AT USA7109MB022 DOT na DOT xerox DOT net>
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7D8967@USA7109MB022.na.xerox.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 30/06/2014 20:04, Nellis, Kenneth wrote:
> Just thought I'd share an observation I found interesting.
> Not a problem for me, so not asking for any particular response.
>
> If I create a named pipe (mkfifo), as long as I write to and read from using
> either 32-bit Cygwin or 64-bit Cygwin, all works fine, but if I write with either
> one and read with the other, both processes hang.
>
> It doesn't seem to matter whether the fifo was created under 32-bit or
> 64-bit, the problem (if I may be so bold as to call it that) seems only with
> mixing 32-/64-bit versions doing I/O to/from it.
>
> FWIW, using 32-bit version 1.7.29-2 and 64-bit version 1.7.30-1.
>
> -Ken Nellis

Hi Ken,
why do you expect such things to work ?
You have two separate simulation layers independent from each other.
Nothing is in place to pass the data from the 32 bit layer to the 64 layer.

Regards
Marco



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