Debugging with GDB: Sparclet

Next: Sparclite, Previous: PA, Up: Embedded Processors [Contents][Index]

#### 21.3.8 Tsqware Sparclet

GDB enables developers to debug tasks running on Sparclet targets from a Unix host. GDB uses code that runs on both the Unix host and on the Sparclet target. The program `gdb` is installed and executed on the Unix host.

`remotetimeout args`

  GDB supports the option `remotetimeout`. This option is set by the user, and args represents the number of seconds GDB waits for responses.

When compiling for debugging, include the options ‘`-g`’ to get debug information and ‘`-Ttext`’ to relocate the program to where you wish to load it on the target. You may also want to add the options ‘`-n`’ or ‘`-N`’ in order to reduce the size of the sections. Example:

    sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N

You can use `objdump` to verify that the addresses are what you intended:

    sparclet-aout-objdump --headers --syms prog

Once you have set your Unix execution search path to find GDB, you are ready to run GDB. From your Unix host, run `gdb` (or `sparclet-aout-gdb`, depending on your installation).

GDB comes up showing the prompt:

    (gdbslet)