This section describes some debugger issues that are specific to cross environments. You will find more information on debugging by reading Debugging.
To connect automatically to the right remote debug agent when
starting a debugging session (using the menu Debug->Initialize),
be sure to specify the Program host and Protocol project
properties, as described in the previous section.
For example, if you are using the Tornado environment, with a target
server called target_ppc, set the Protocol to wtx and
the Program host to target_ppc.
Once the debugger is initialized, you can also connect to a remote agent
by using the menu Debug->Debug->Connect to Board.... This will open
a dialog where you can specify the target name (e.g. the name of your
board or debug agent) and the communication protocol.
In order to load a new module on the target, you can select the menu
Debug->Debug->Load File....
If a module has been loaded on the target and is not known
to the current debug session, use the menu
Debug->Debug->Add Symbols... to load the symbol tables in the current
debugger.
Similarly, if you are running the underlying debugger (gdb) on a remote
machine, you can specify the name of this machine by setting the
Tools host field of the project properties.