Hi all,

I've started some work towards getting mspgcc compatible with the current bleeding edge GDB, so that integration with the main GDB project is possible.

First the good news. Since MSP430 support was merged with the main binutils project, a lot of what is needed for MSP430 support in GDB is also in the recent snapshots of GDB. This is because they share a lot of modules, and the same CVS tree at sources.redhat.com. I have started a gdb/gdb-5.4 tree in the mspgcc CVS (and screwed something up, which I have asked the SourceForge admins to clean up for me). Some of files in this are from this week's weekly snapshot of GDB at sources.redhat.com, with just one or two lines changed for MSP430 compatibilty (e.g. the make files).

Now the bad news. The remainder of the files in gdb/gdb-5.4 are the MSP430 specific stuff which are not common to binutils. They need to be *very* different from the versions we have been using with GDB 5.1.1. In the spring, Dmitry posted a version of msp430-tdep.c which tried to be compatible with the newer GDBs. The latest CVS has changed a lot from even that. Many of the function calls Dmitry added now have their names changed to add "_deprecated_" in the middle. It seems the pace of change is fast in the GDB project!

I have been making changes towards getting GDB to at least compile as an MSP430 tool. It only gives a few errors now, but is far from being complete.

Well, that is the current state of play. This work really needs to be moved forward. Many nice tools (e.g. Eclipse) are compatible with only the most recent versions of GDB. We need to keep up. :-)

Regards,
Steve



Reply via email to