From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30830 invoked by alias); 30 Jun 2011 22:50:45 -0000 Received: (qmail 30820 invoked by uid 22791); 30 Jun 2011 22:50:44 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.44.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Jun 2011 22:50:27 +0000 Received: from kpbe11.cbf.corp.google.com (kpbe11.cbf.corp.google.com [172.25.105.75]) by smtp-out.google.com with ESMTP id p5UMoQkj032519 for ; Thu, 30 Jun 2011 15:50:26 -0700 Received: from yib19 (yib19.prod.google.com [10.243.65.83]) by kpbe11.cbf.corp.google.com with ESMTP id p5UMoI6o027290 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Thu, 30 Jun 2011 15:50:25 -0700 Received: by yib19 with SMTP id 19so1599405yib.23 for ; Thu, 30 Jun 2011 15:50:25 -0700 (PDT) Received: by 10.151.87.14 with SMTP id p14mr2433090ybl.145.1309474225176; Thu, 30 Jun 2011 15:50:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.7.14 with HTTP; Thu, 30 Jun 2011 15:49:55 -0700 (PDT) In-Reply-To: <4E0CF948.6030303@rawbw.com> References: <4D0AD70D.9020702@rawbw.com> <4E0CF948.6030303@rawbw.com> From: Paul Pluzhnikov Date: Thu, 30 Jun 2011 22:50:00 -0000 Message-ID: Subject: Re: Why gdb-7.1 doesn't set hardware watchpoints on i7 CPU (amd64)? To: Yuri Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-06/txt/msg00179.txt.bz2 On Thu, Jun 30, 2011 at 3:31 PM, Yuri wrote: > On 12/26/2010 21:06, Paul Pluzhnikov wrote: >> >> You begin by explaining what made you conclude that you can't set HW >> watchpoints, preferably by showing a sample program and a complete log >> of your GDB session. Verifying that the same problem exists in current >> CVS snapshot is also a good idea. You didn't show *complete* log of your GDB session. This leaves us to guess which version of GDB you are using (your message says 7.2), and what platform it was configured for. Verifying that the problem exists in latest CVS snapshot is *still* a good idea. > This happens on all programs. > I "conclude" by seeing that it prints "Watchpoint" not "Hardware watchpoint" > and observing a very slow execution after it is set. > > (gdb) watch *(char*)0x3c74340 > Watchpoint 6: *(char*)0x3c74340 > (gdb) c > <...very long wait...> Is 0x3c74340 addressable at the point where you set the watch? (This also likely would have been answered by a complete log of your GDB session.) Cheers, -- Paul Pluzhnikov