On Sun, 27 Oct 2002, Mark Burton wrote:

> I've been diffing aobut in the latest GDB sources and it looks pretty
> complex. It's all written in C, which I find a bit of a pain to read. My
> day job is a C++ programmer :)
>
> I think what I'll do is work on the PIC code and implement GDB's remote
> protocol. If I can read & write memory and maybe set break points, even
> if it means using hyper terminal, then I'll be happy. I'm still learning
> PIC assembler so it's a nice little project.

If you're just learning PIC assembler, then this would be a nice *big*
project. gpsim has over 60,000 lines of code and it's still not done.
Perhaps only 20,000 or so are just simulation related and perhaps only a
fraction (50%?) of that would be needed in a gdb port. Of course, if you
just wanted the very basic (instruction emulation) then maybe only 3000
would be all you need to write. No matter how you slice it, this is not a
little project. BTW, why would you want to use hyper term?

Just for grins, gdb-5.2 for the arm-elf tools weighs in at 340,000 lines
of code! Of course, not all of that was created for the ARM port. But I
suppose you'd have to sift through a good portion of that to do a new
port.

Scott

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.