Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: dave.anglin@nrc-cnrc.gc.ca, Mark Kettenis <kettenis@gnu.org>,
	  brobecker@adacore.com,  gdb@sourceware.org
Subject: Re: Likely obsolete pieces of GDB
Date: Sat, 10 Feb 2007 21:42:00 -0000	[thread overview]
Message-ID: <45CE3C17.8080802@portugalmail.pt> (raw)
In-Reply-To: <20061216212254.GA14335@trixie.casa.cgf.cx>

Christopher Faylor escreveu:
> On Sat, Dec 16, 2006 at 03:59:23PM -0500, Daniel Jacobowitz wrote:
>> wince-stub.c
>> wince-stub.h
>> wince.c
>>
>> 	For Windows CE devices.  Pedro Alves breathed some life
>> 	back into these in June, but Chris Faylor rejected the
>> 	patch (with which I completely agree).  It's a Windows-specific
>> 	remote protocol, and should use the GDB remote protocol
>> 	instead.
>>
>> 	And now there's a Windows gdbserver as a start to that.
>> 	I think these files should be removed.
> 
> And, it should come as no surprise that I agree and I apologize
> for introducing this misbegotten code into gdb to begin with.
> 

(Sorry for taking such a long time to reply to this, I was internet-less
for a month.)

Looking at my patch now, I now fully agree with the rejection.  Thank you
for rejecting it. :)

I have the WinCE gdbserver port 99% ready for submission.  There are just
a few other things I would like to solve first: is the target
name that I have been calling arm-wince-mingw32ce at cegcc.sourceforge.net
ok, or should I rename it?;  Some cleanups at the mingw32ce side, that are
needed for the gdbserver;  Submit a few gdb fixes that are either global
or PE related.

Removing the current wince support now, means that I will have to add
a few things back again later (mostly autoconf stuff, and the
target header), but there's no problem with me, if it is wanted.
Else, I will remove them with the gdbserver port.

Cheers,
Pedro Alves



  reply	other threads:[~2007-02-10 21:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 20:59 Daniel Jacobowitz
2006-12-16 21:23 ` Christopher Faylor
2007-02-10 21:42   ` Pedro Alves [this message]
2007-02-10 23:50     ` Daniel Jacobowitz
2007-02-19  1:25       ` Pedro Alves
2006-12-17  1:24 ` John David Anglin
2006-12-17 11:46   ` Mark Kettenis
2007-01-01 16:34     ` Daniel Jacobowitz
2006-12-18  3:03   ` John David Anglin
2006-12-18  3:43     ` John David Anglin
2006-12-20 16:07     ` John David Anglin
2006-12-20 17:41       ` John David Anglin
2007-01-01 16:33         ` Daniel Jacobowitz
2007-01-01 16:47           ` John David Anglin
2007-01-01 17:10             ` Mark Kettenis
2007-01-01 17:20               ` John David Anglin
2006-12-17  1:36 ` Russell Shaw
2006-12-17 12:20 ` Mark Kettenis
2006-12-17 14:26   ` Stephen & Linda Smith
2006-12-17 15:37   ` Daniel Jacobowitz
2006-12-20  6:01     ` Joel Brobecker
2006-12-17 13:40 ` Joel Brobecker
2007-01-01 16:46 ` Daniel Jacobowitz
2007-01-01 16:58   ` Mark Kettenis
2007-01-03 23:55   ` Jim Blandy
2007-02-10 20:50   ` Daniel Jacobowitz
2007-02-12 17:35     ` Joel Brobecker

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=45CE3C17.8080802@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=brobecker@adacore.com \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=gdb@sourceware.org \
    --cc=kettenis@gnu.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