X-Spam-Check-By: sourceware.org
Message-ID: <76366b180612041935t15e72332mf675b5867f7b2a96@mail.gmail.com>
Date: Mon, 4 Dec 2006 22:35:35 -0500
From: "Andrew Paprocki" <andrew AT ishiboo DOT com>
To: cygwin AT cygwin DOT com
Subject: cygwin + vista x64
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: 06129d30a13799b3
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

Corinna,

I've been trying to figure out why cygwin isn't working properly on
Vista x64. I saw the thread you posted to here:

http://www.cygwin.com/ml/cygwin/2006-11/msg00595.html

I see that cygwin is performing the trick outlined here:

http://www.catch22.net/tuts/undoc01.asp

(Search for "Pass arbitrary data to a child process!")

This is achieved because the child_info class is declared to have:

DWORD zero[4]; // must be zeroed

It appears as if this trick is no longer working under Vista x64. The
question is, does this code now have to resort to using
VirtualAllocEx/WriteProcessMemory, or is there a way around it?

Have you been able to isolate this into a simple binary test? I am
currently running on a Vista x64 system right now with VS2005
installed in case you would like me to try out anything which may be
of help.

-Andrew

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/