From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3351 invoked by alias); 14 Jan 2009 13:00:59 -0000 Received: (qmail 3342 invoked by uid 22791); 14 Jan 2009 13:00:58 -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:00:17 +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 n0ED05Jp004035; Wed, 14 Jan 2009 14:00:10 +0100 In-Reply-To: <000001c9763a$4d6cda90$e8468fb0$@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:00:00 -0000 Content-Type: text/plain; charset="US-ASCII" 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/msg00310.txt.bz2 gdb-patches-owner@sourceware.org wrote on 14.01.2009 12:21:53: > 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... For address above 4GB hardware watchpoints aren't working, reasoned by truncation. > 2) Is GetThreadSelectorEntry function > working in win64 ? > The reason of the question is that > I have no win64 machine... so that I cannot test directly, > the windows SDK says that it only works on i386 based > machines, but that is sort of vague. > Furthermore, the base address that is computed > with this function is a 32bit address, so I am > wondering if it is meaningful or not... Yes, it is present, but I am not sure if structure has still the same layout. > The reason of the second question is that I have a > patch that is able to display the thread information block > and the structured exception handler chain on > a win32 program, but I did not find much information on > the the win64 equivalent, apart from the fact > that it is apparently the $gs selector that is > used on x86_64 in windows64, instead of the $fs for win32. Cheers, Kai | (\_/) This is Bunny. Copy and paste Bunny | (='.'=) into your signature to help him gain | (")_(") world domination.