X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: mwoehlke Subject: Re: Thread Injection + Cygwin problems Date: Tue, 20 Jun 2006 11:40:15 -0500 Lines: 26 Message-ID: References: <449729AA DOT 4030007 AT arkasoft DOT com> <20060620142945 DOT GH19534 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.4 (X11/20060516) In-Reply-To: <20060620142945.GH19534@trixie.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Faylor wrote: > On Mon, Jun 19, 2006 at 06:11:57PM -0500, mwoehlke wrote: >> Kaveh Goudarzi wrote: >>> I've written a program to detect the invocation of processes and then >>> inject them with a remote thread in the hope of getting the cmdLine/cwd >>> and environment variables of the running process. >> [snip] >>> I'm not sure how to approach the problem so any advice would be greatly >>> appreciated. >>> >>> Is there an obvious reason why attempting to invoke cygwin calls such >>> as getenv() in an injected thread might result in crashes? I've also >>> tried cygwin_internal(CW_SYNC_WINENV) with the same result. I'm >>> running Windows XP and have tried the 20060614 snapshot with the same >>> result. >> There are known problems with thread injection and Cygwin. Are you >> using the latest cygwin.dll snapshot? > > He said he was running the latest version of the snapshot (I put back > the part that you snipped above). Missed that; my apologies. -- Matthew The hippo made me do it! What? What do you mean you can't see the hippo? -- 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/