Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <42FB89AC.2050801@club-internet.fr>
Date: Thu, 11 Aug 2005 19:23:56 +0200
From: Louis Lecaroz <louis DOT lecaroz AT club-internet DOT fr>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Louis Lecaroz <louis DOT lecaroz AT club-internet DOT fr>
Cc: cygwin AT cygwin DOT com
Subject: Re: "Segmentation fault" CygWin tools with code Injection-MS Detours
References: <42FB7644 DOT 8020905 AT le-resistant DOT com> <20050811163305 DOT GB6935 AT trixie DOT casa DOT cgf DOT cx> <42FB7FF2 DOT 3020709 AT club-internet DOT fr>
In-Reply-To: <42FB7FF2.3020709@club-internet.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

So to be more clear on my previous post (sorry, english is not my 
natural language :( ) :
-The LD_PRELOAD is not performed (It appears not to be performed...) in 
the forkee, so the code is not loaded in it (I think)
-Yes, I would like the LD_PRELOAD to be loaded in the forkee, this will 
allow also my code to be loaded in the forkee.
Finaly I suppose in term of code, not performing  a setjmp/longjmp 
directly to the same CS:IP location in the forkee but to a stub in the 
cygwin library, loading the LD_PRELOAD & next jumping itself to the same 
CS:IP as requested in the parent... Am I right ? This question is to be 
sure, I have understand everything correctly & I have exposed my issue 
also correctly ;)
& also to increase my knowledges on the cygwin code behavior ;)

Thx in advance,
Louis

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