From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-6824-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 9706 invoked by alias); 17 Nov 2001 01:10:31 -0000
Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 9680 invoked from network); 17 Nov 2001 01:10:28 -0000
Received: from unknown (HELO cygnus.com) (205.180.230.5)
  by sourceware.cygnus.com with SMTP; 17 Nov 2001 01:10:28 -0000
Received: from loony.cygnus.com (loony.cygnus.com [205.180.230.181])
	by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id RAA24439
	for <gdb@sources.redhat.com>; Fri, 16 Nov 2001 17:10:27 -0800 (PST)
Received: (from cgf@localhost)
	by loony.cygnus.com (8.11.6/8.8.7) id fAH1AVQ19514
	for gdb@sources.redhat.com; Fri, 16 Nov 2001 20:10:31 -0500
Date: Tue, 06 Nov 2001 19:34:00 -0000
From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: x86 hardware breakpoint question
Message-ID: <20011117011031.GC19468@redhat.com>
Mail-Followup-To: gdb@sources.redhat.com
References: <20011116205455.GA18328@redhat.com> <20011115125927.B3449@atlas.lcs.mit.edu> <20011115125927.B3449@atlas.lcs.mit.edu> <4.2.0.58.20011116135651.0128d658@ics.u-strasbg.fr> <2593-Fri16Nov2001184752+0200-eliz@is.elta.co.il> <20011116205455.GA18328@redhat.com> <3.0.6.32.20011117000436.00b05380@ics.u-strasbg.fr> <200111162257.fAGMv4f12497@greed.delorie.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200111162257.fAGMv4f12497@greed.delorie.com>
User-Agent: Mutt/1.3.23.1i
X-SW-Source: 2001-11/txt/msg00071.txt.bz2

On Fri, Nov 16, 2001 at 05:57:04PM -0500, DJ Delorie wrote:
>
>>   So I am surprised to hear that win32
>> lets you set debug registers, but if that works, great!
>
>I don't know if it works, I just looked it up in the documentation.
>
>>  Are the debug registers process wide or
>> thread specific in that case ?
>
>Well, it is Set*Thread*Context.

Which is, conveniently enough, what gdb is already using.  :-)

Did you find specific documentation on the hardware registers, though?

I see this in the system header:

    BYTE    ExtendedRegisters[MAXIMUM_SUPPORTED_EXTENSION];

but I don't see any description about how to use them.

cgf