[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[cdt-debug-dev] New CDT/Debug targets (was: PalmOS Patches)
|
>
>
> --=-Lks+qVb5IX9oUsVKYB2p
> Content-Type: multipart/mixed; boundary="=-R3tx/zANWt0BEte7zqaA"
>
>
> --=-R3tx/zANWt0BEte7zqaA
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> On Wed, 2003-07-09 at 01:05, Daniel Thompson wrote:
> > I am currently using the attached (tiny) patch to provide rudimentary
> ^^^^^^^^
>
> Bum!
>
8-)
> Attached this time.
>
Not sure, we want to do this. Although we've accept the "GDB Server"
and the "Cygwin GDB Debugger", it was more for convenience(although
some purists here still argue it was a mistake 8).
The real problem is the maintainance of the CDT/Debug code base
with the proliferation of targets. No resources and simply no way
to test them all.
We've already turn down "Oyvind Harboe" patches for the "Ecos GDB Arm cpu"
although like yours the changes were fairly simple,(He has however more
problem with gdb crashing then CDT 8-).
Distributing the code in a new plugin is probably better(no problem for
you to have access to the code and distribute new versions) and as efficient
as having it in the org.eclipse.cdt.debug.mi.core plugin.
Note:
We were suppose to have a CDT contribution plugin repository, where the community
could put those usefull little tinbits ...