Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Working on the x86_64-windows native port...
Date: Thu, 13 Nov 2008 22:45:00 -0000	[thread overview]
Message-ID: <20081113224430.GJ10146@adacore.com> (raw)

[ChrisF, I noticed you prefer if we don't Cc you in addition to reaching
through the mailing-list. I work a little differently, so hopefully
you'll see this message]

Hello everyone,

Just a quick message to say that I started looking at porting GDB to
x86_64-windows. Currently, if I use a 32bit compiler and configure
GDB as a i686-pc-mingw32, I get a fine debugger.

Things get a little more interesting when I use a 64bit compiler
and configure GDB with x86_64-pc-mingw32 [1]. Basically, the root
of the issues I am seeing comes from the fact that win32-nat has
some ia32-specific code, in particular in terms of the registers
(see the CONTEXT structure for instance).

My intentions are to split off the 32bit-specific parts to
i386-windows-nat.c, and write the equivalent x86_64-windows-nat.c.
I hope that's OK with everyone (Chris?).

-- 
Joel

[1]: Currently, config.guess (IIRC) doesn't like mingw64. For now,
     I'll keep mingw32 as meaning either 32bit or 64bit. I'll probably
     fix this too, but later.


             reply	other threads:[~2008-11-13 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 22:45 Joel Brobecker [this message]
2008-11-13 23:00 ` Christopher Faylor
2008-11-15 17:45   ` Joel Brobecker
2008-11-25 17:33     ` Kai Tietz
2008-11-25 19:21       ` Joel Brobecker
2008-11-13 23:08 ` Mark Kettenis
2008-11-14  9:15 ` Kai Tietz

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=20081113224430.GJ10146@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@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