From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23558 invoked by alias); 14 Jan 2009 13:31:18 -0000 Received: (qmail 23532 invoked by uid 22791); 14 Jan 2009 13:31:13 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from outdoor.onevision.de (HELO outdoor.onevision.de) (212.77.172.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Jan 2009 13:30:23 +0000 Received: from sanders.onevision.de (moonrace [212.77.172.62]) by outdoor.onevision.de (8.14.3/8.13.7/ROSCH/DDB) with ESMTP id n0EDUFRL009606; Wed, 14 Jan 2009 14:30:20 +0100 In-Reply-To: <000d01c9764a$2e08b5b0$8a1a2110$@u-strasbg.fr> To: "Pierre Muller" Cc: gdb-patches@sourceware.org Subject: RE: [RFC] 32-bit support for windows thread information block MIME-Version: 1.0 Message-ID: From: Kai Tietz Date: Wed, 14 Jan 2009 13:31:00 -0000 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00312.txt.bz2 "Pierre Muller" wrote on 14.01.2009 14:15:32: >=20 >=20 > > -----Message d'origine----- > > De : gdb-patches-owner@sourceware.org [mailto:gdb-patches- > > owner@sourceware.org] De la part de Kai Tietz > > Envoy=E9 : Wednesday, January 14, 2009 2:00 PM > > =C0 : Pierre Muller > > Cc : gdb-patches@sourceware.org > > Objet : Re: [RFC] 32-bit support for windows thread information block > >=20 > > gdb-patches-owner@sourceware.org wrote on 14.01.2009 12:21:53: > >=20 > > > I implemented two new command that display > > > a part of the information of the > > > thread information block and on > > > the structured exception handler chain. > > > I added these two command to the "info w32" command > > > prefix, but got into troubles appearing below. > > > > > > I have several questions regarding the 64-bit support of > > > windows nat files: > > > > > > 1) Do hardware watchpoints work? > > > the problem is that the dr[8] array is > > > defined as a unsigned type, > > > is this enough for win64? > > > Is "unsigned" type a 64-bit ? > > > > > > In the _CONTEXT struct > > > the debug registers are defined as DWORD64... > >=20 > > For address above 4GB hardware watchpoints aren't working, reasoned by > > truncation. >=20 > This would be easily fixed by changing the=20 > "unsigned" type into something that would be > "DWORD64" on 64-bit and "DWORD" on 32-bit. >=20 > The main problem for me is that I don't know=20 > what would be a reasonable choice for that type? >=20 > Would uintptr_t be OK here? uintptr_t would be fine. DWORD_PTR would be the ms answer for this, but=20 isn't CORE_ADDR the better choise here? Cheers, Kai | (\_/) This is Bunny. Copy and paste Bunny | (=3D'.'=3D) into your signature to help him gain | (")_(") world domination.