Note that the information below concerns debugging under elinux. For information about debugging under the Linux 2.4 port, please refer to the gdb-cris pages.Q - How do I debug my elinux developer board application?
A - One of the advantages with the developer board running Linux is that you can compile, run, and debug your application on your desktop Linux machine (or any Unix flavour that supports the libraries etc that your application is depending on). This eliminates much of the traditional need for remote debugging over a serial line, which is what you typically do with an embedded system.
Q - My application fails on the elinux developer board, but works fine on my desktop Linux machine. What do I do next?
A - The ability to develop your application on your desktop machine also means that you are able to benefit from more powerful debugging tools, which normally aren't available in an embedded environment. Examples include libraries such as efence, for hunting down memory leaks and buffer overwrites. In case your application relies on uC-libc (the C library in Linux for the ETRAX), which won't be available on your desktop Linux machine, your program's environment differs between the developer board and your desktop Linux machine. If your application runs perfectly fine on your desktop Linux machine, but fails on the developer board, your best strategy is deploying printfs in the code.
Q - What's the reason for not being able to do remote debugging of my applications?
A - As you might know, Linux for the ETRAX 100 uses a rom file system from which applications are loaded into memory during the developer board's boot sequence. This prevents traditional debugging with a gdb stub, since gdb is not able to figure out where in the devboard's memory an application is running.
Q - I have problems installing the compiler tools package in cris-dist-1.7 with Red Hat 7.0
A - Usekgccwhen compiling that version. Where you would write./install-cris-tools, instead writeenv CC=kgcc ./install-cris-tools.