Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb-patches@sourceware.org
Cc: drow@false.org
Subject: Re: [PATCH] Windows CE support update.
Date: Tue, 20 Jun 2006 23:35:00 -0000	[thread overview]
Message-ID: <44988631.3010606@portugalmail.pt> (raw)
In-Reply-To: <20060620201214.GA1278@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Tue, Jun 20, 2006 at 04:09:01PM -0400, Christopher Faylor wrote:
>   
>> Also, I really don't want to pollute the win32-nat.c file with CE
>> accommodations.  That would again make me the de facto maintainer of
>> Windows CE - a role from which which I've previously abdicated.
>>
>> So, thanks very much for the patch.  It was obviously a lot of work but
>> I really don't want to do things this way.
>>     
>
> I thoroughly agree.
>
> Pedro, if you are motivated to work on this - obviously we'd understand
> if you'd rather just use what you've got - I'd be happy to discuss any
> improvements to the remote protocol that you needed.
>
>   
Thanks, but I will pass on this for now.
I hope I will get back to this, I sure had fun hacking gdb, but, since 
free time is limited, I will shift my priorities.

Anyway, for reference, can you point to any gdbserver/remote stub effort 
for win32 (other than gdbproxy)?
There doesn't seem to be anything of the sort in gdb/

Cheers,
Pedro Alves


  reply	other threads:[~2006-06-20 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 12:54 Pedro Alves
2006-06-20 20:09 ` Christopher Faylor
2006-06-20 20:12   ` Daniel Jacobowitz
2006-06-20 23:35     ` Pedro Alves [this message]
2006-06-20 23:36       ` Daniel Jacobowitz
2006-06-20 23:55         ` Pedro Alves
2006-06-20 23:27   ` Pedro Alves
2006-06-26 20:39     ` Kevin Buettner

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=44988631.3010606@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=drow@false.org \
    --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