From: Pedro Alves <pedro@codesourcery.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Mingw Windows 64-bit gdbserver
Date: Fri, 16 Apr 2010 16:27:00 -0000 [thread overview]
Message-ID: <201004161727.26943.pedro@codesourcery.com> (raw)
In-Reply-To: <001901cadd80$b476aff0$1d640fd0$@muller@ics-cnrs.unistra.fr>
On Friday 16 April 2010 17:20:18, Pierre Muller wrote:
> > How about instead merging the files, like
> > linux-x86-low.c handles both 64-bit and 32-bit? There's
> > a lot of common stuff between both archs support, it
> > seems.
> Yes, but ...
> > Also, is there any debug API limitation that would
> > make it impossible for a 64-bit gdbserver to debug a 32-bit
> > inferior (that is, multi-arch the Windows gdbserver)?
> It not impossible, but it doesn't work
> without using some new API functions:
> Wow64GetThreadContext, Wow64GetThreadSelectorEntry,
> and Wow64SetThreadContext
>
> See http://msdn.microsoft.com/en-us/library/ms679303%28VS.85%29.aspx
>
> This would also be required to be able to debug win32
> application within a windows 64-bit GDB executable.
>
> Implementing this is probably a larger patch than this one ...
I didn't mean to suggest you work on that. Merely to
consider if once we implement that, we'll end up merging
the files anyway...
> > That being possible would be another reason to just merge
> > the files up from the start.
>
> So that argument falls!
Of course it doesn't. But okay, let's keep them appart
anyway. Easy to merge any other time.
> > > - About the used communication library:
> > > -lwsock32 was not found by the mingw, but main gdb
> > > doesn't seem to use it, should we move to ws2_32 for both win32 and
> > win64?
> >
> > Don't we need to make gdbserver include windows2.h instead of winsock.h
> > too?
>
> No, I only found #include <windows.h>
Typo: I meant winsock2.h instead of winsock.h.
--
Pedro Alves
next prev parent reply other threads:[~2010-04-16 16:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 15:32 Pierre Muller
2010-04-16 15:59 ` Pedro Alves
2010-04-16 16:20 ` Pierre Muller
2010-04-16 16:27 ` Pedro Alves [this message]
2010-04-16 16:38 ` Pierre Muller
2010-04-16 17:15 ` Pedro Alves
2010-04-17 5:39 ` [RFA] Use winsock2 for mingw gdbserver Pierre Muller
2010-04-17 8:28 ` Pedro Alves
2010-04-17 20:44 ` Pierre Muller
2010-04-17 5:40 ` [RFC] Mingw Windows 64-bit gdbserver Pierre Muller
2010-04-17 10:58 ` Pedro Alves
2010-04-17 23:18 ` [RFC-v2] " Pierre Muller
2010-04-17 23:46 ` Pedro Alves
2010-04-19 6:37 ` [RFA] Prepare for " Pierre Muller
[not found] ` <6200558430975530197@unknownmsgid>
2010-04-19 13:56 ` H.J. Lu
2010-04-19 14:13 ` Pierre Muller
2010-04-16 16:27 [RFC] " Ozkan Sezer
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=201004161727.26943.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.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