From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14057 invoked by alias); 27 Dec 2010 05:07:21 -0000 Received: (qmail 14049 invoked by uid 22791); 27 Dec 2010 05:07:20 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_20,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) (74.125.121.67) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Dec 2010 05:07:14 +0000 Received: from hpaq2.eem.corp.google.com (hpaq2.eem.corp.google.com [172.25.149.2]) by smtp-out.google.com with ESMTP id oBR57BMv011640 for ; Sun, 26 Dec 2010 21:07:11 -0800 Received: from qyk7 (qyk7.prod.google.com [10.241.83.135]) by hpaq2.eem.corp.google.com with ESMTP id oBR56saO029038 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Sun, 26 Dec 2010 21:07:10 -0800 Received: by qyk7 with SMTP id 7so9508379qyk.7 for ; Sun, 26 Dec 2010 21:07:09 -0800 (PST) Received: by 10.224.37.131 with SMTP id x3mr11372771qad.199.1293426429377; Sun, 26 Dec 2010 21:07:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.67.222 with HTTP; Sun, 26 Dec 2010 21:06:39 -0800 (PST) In-Reply-To: <4D0AD70D.9020702@rawbw.com> References: <4D0AD70D.9020702@rawbw.com> From: Paul Pluzhnikov Date: Mon, 27 Dec 2010 05:07: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: 2010-12/txt/msg00074.txt.bz2 On Thu, Dec 16, 2010 at 7:20 PM, Yuri wrote: > All watchpoints are software. > How can I troubleshoot? How to understand why its unable to set HW > watchpoints? 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. Hope this helps, Happy Holidays! -- Paul Pluzhnikov