X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <47127845.5000905@portugalmail.pt> Date: Sun, 14 Oct 2007 21:12:53 +0100 From: Pedro Alves User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [gdb] Data watchpoints in Windows weirdness. Call for testers. References: <4702E6B7 DOT 8020100 AT portugalmail DOT pt> <20071008124331 DOT GD19254 AT calimero DOT vinschen DOT de> <20071008143552 DOT GA20746 AT ednor DOT casa DOT cgf DOT cx> <47115BEF DOT 7030407 AT portugalmail DOT pt> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 René Berber wrote: (...) > Program received signal SIGTRAP, Trace/breakpoint trap. > main () at main.c:18 > 18 Sleep (1000); > (gdb) p count > $3 = 1001 > (gdb) c > Continuing. > Hardware watchpoint 2: count > > Old value = 0 > New value = 1002 (...) Thanks! That clearly shows the exact same problem. Somehow, the code in the while(1) loop starts behaving, and for the same executable, the symptom manifests exactly across machines. If one tweaks the program a little, the problem shows up in different lines. Could you tell me what version of Windows was that? I'd be perfect if someone with access to a Windows != XP machine could do the same test. Cheers, Pedro Alves -- 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/