X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 8 Oct 2007 14:43:31 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [gdb] Data watchpoints in Windows weirdness. Call for testers. Message-ID: <20071008124331.GD19254@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4702E6B7 DOT 8020100 AT portugalmail DOT pt> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4702E6B7.8020100@portugalmail.pt> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 On Oct 3 01:47, Pedro Alves wrote: > By a long shot, Cygwin doesn't do anything funny like hooking > GetThreadContext, does it? cgf might be better suited to answer this, but AFAICS, Cygwin doesn't hook any system function. It just uses them. OTOH, there are two calls to SetThreadContext in Cygwin, both of them changing Eip. Could that be a problem? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/