...
- It is not a full source code debugger
- It requires a USB cable and JTAG dongle to talk to the target
- Thread-related commands, e.g., "info thread" or "thread 1", don't work
Here's an example XMD session:
...
The implementation developed at SSRL requires some patches to GDB in order to run. This patched version of GDB is available via the DAT group's AFS space in /afs/slac/g/cci/package/gnu or in /reg/common/package/gnu/rtems-4.10/bin if AFS is not available. Also, the core code on the RCE must have the GDB stub compiled in and started automatically. This is true as of core 1.3 (commit 1135). Note: the GDB daemons only run on the development core, not in the production core.
...
- Create two windows, one on the GDB host, and one for telnetting to the RCE.
- Start GDB against the version of the development core that is on the RCE
Code Block /reg/lab1/home/panetta/bin/powerpc-rtemsrtems4.10-gdb build/rceapp/bin/ppc-rtems-rce405-dbg/core.1.2.devel
- Connect GDB to the RCE over port 2159 (Ignore the warning. Steve says that this will be normal.)
Code Block (gdb) target rtems-remote rce48:2159 Remote debugging using rce48:2159 [New Thread a01000a] [Switching to Thread a01000a] BREAKPOINT () at /reg/lab1/home/panetta/petacache/rce/gdbstub/rtems-gdb-stub-ppc-shared.h:20 20 } warning: /reg/lab1/home/panetta/petacache/build/rceapp/bin/ppc-rtems-rce405-dbg/core.1.2.devel: '.text' section of executable file doesn't match the target's -- do GDB and the target use the same file? Current language: auto; currently c++ (gdb)
...