From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-39459-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 29288 invoked by alias); 30 Jun 2011 22:31:55 -0000
Received: (qmail 29280 invoked by uid 22791); 30 Jun 2011 22:31:55 -0000
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from shell0.rawbw.com (HELO shell0.rawbw.com) (198.144.192.45)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Jun 2011 22:31:39 +0000
Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1])	(authenticated bits=0)	by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id p5UMP5Ig054635;	Thu, 30 Jun 2011 15:25:05 -0700 (PDT)	(envelope-from yuri@rawbw.com)
Message-ID: <4E0CF948.6030303@rawbw.com>
Date: Thu, 30 Jun 2011 22:31:00 -0000
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101211 Thunderbird/3.0.11
MIME-Version: 1.0
To: Paul Pluzhnikov <ppluzhnikov@google.com>
CC: gdb@sourceware.org
Subject: Re: Why gdb-7.1 doesn't set hardware watchpoints on i7 CPU (amd64)?
References: <4D0AD70D.9020702@rawbw.com> <AANLkTinq0Tik8LU70aV81xsNeFi8=mKVvzbb1xp4s_qV@mail.gmail.com>
In-Reply-To: <AANLkTinq0Tik8LU70aV81xsNeFi8=mKVvzbb1xp4s_qV@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-06/txt/msg00178.txt.bz2

On 12/26/2010 21:06, Paul Pluzhnikov wrote:
> On Thu, Dec 16, 2010 at 7:20 PM, Yuri<yuri@rawbw.com>  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.
>    

Sorry, I missed your reply.
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...>

Yuri