Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Kai Tietz'" <Kai.Tietz@onevision.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] 32-bit support for windows thread information block
Date: Wed, 14 Jan 2009 13:16:00 -0000	[thread overview]
Message-ID: <000d01c9764a$2e08b5b0$8a1a2110$@u-strasbg.fr> (raw)
In-Reply-To: <OFBE13041F.7FC09774-ONC125753E.004410CB-C125753E.00476A4F@onevision.de>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Kai Tietz
> Envoyé : Wednesday, January 14, 2009 2:00 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] 32-bit support for windows thread information block
> 
> 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.

  This would be easily fixed by changing the 
"unsigned" type into something that would be
"DWORD64" on 64-bit and "DWORD" on 32-bit.

  The main problem for me is that I don't know 
what would be a reasonable choice for that type?

  Would uintptr_t be OK here?



Pierre Muller
Pascal language support maintainer for GDB





  reply	other threads:[~2009-01-14 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 11:22 Pierre Muller
2009-01-14 13:00 ` Kai Tietz
2009-01-14 13:16   ` Pierre Muller [this message]
2009-01-14 13:31     ` Kai Tietz
2009-01-14 14:44       ` [RFC] 64-bit support for x86-64 windows debug registers Pierre Muller
2009-01-15 10:08         ` Kai Tietz
2009-01-16 10:39           ` [RFA/windows] " Pierre Muller
2009-01-16 20:11             ` Christopher Faylor
2009-01-19  8:59               ` Pierre Muller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000d01c9764a$2e08b5b0$8a1a2110$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=Kai.Tietz@onevision.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox