Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kai Tietz <Kai.Tietz@onevision.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] 64-bit support for x86-64 windows debug registers
Date: Thu, 15 Jan 2009 10:08:00 -0000	[thread overview]
Message-ID: <OF1A18057F.07048706-ONC125753F.00376FB3-C125753F.00379CAC@onevision.de> (raw)
In-Reply-To: <001401c97656$77a66b70$66f34250$@u-strasbg.fr>

"Pierre Muller" <muller@ics.u-strasbg.fr> wrote on 14.01.2009 15:43:29:

>   Following Kai's advice, I modified the
> windows-nat.c code to use 
>   CORE_ADDR for dr0 to dr3,
> but I left the type unchanged for 
> dr6 and dr7, as, after reading the 
> amd64 specifications, I saw that those fields
> remain 32-bit wide.
> 
>   I could only test it with on 32 cygwin,
> but at least it also works with 
> --enable-targets=all --enable-64-bit-bfd
> options.
> 
> Kai,
> could you test this out, please?

Hello Pierre,

for me it worked fine on w64. But of course a maintainer has to give his 
approval for this. 

Cheers,
Kai

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.


  reply	other threads:[~2009-01-15 10:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 11:22 [RFC] 32-bit support for windows thread information block Pierre Muller
2009-01-14 13:00 ` Kai Tietz
2009-01-14 13:16   ` Pierre Muller
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 [this message]
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=OF1A18057F.07048706-ONC125753F.00376FB3-C125753F.00379CAC@onevision.de \
    --to=kai.tietz@onevision.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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