On Wed, May 11, 2011 at 6:22 AM, Peter Bigot <big...@acm.org> wrote: > As Eric says, for now the old gdb seems to work. If you don't want to pull > it out of the mspgcc4 tar file, then clone this git repository: > > git://mspgcc.git.sourceforge.net/gitroot/mspgcc/gdb > > and check out the legacy/release/gdb-7.2 branch. This should be exactly > what's in the mspgcc4 distribution, but all patched and ready to go.
I am having some troubles here, but this could be entirely because I don't really have a clue what I'm supposed to be doing. I built gdb like this: git clone git://mspgcc.git.sourceforge.net/gitroot/mspgcc/gdb cd gdb git checkout remotes/origin/legacy/release/gdb-7.2 ./configure; make; make install I gather that mspdebug is the way to go here, and this seems to set things up: mspdebug rf2500 gdb Then I fire up gdb, and issue: target remote localhost:2000 Which errors out with: Remote debugging using localhost:2000 Reply contains invalid hex digit 59 And in the process, mspdebug closes the connection. Am I doing this at all right? -p. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
