Changes

==Remote Debugging with GDB==

==Remote Debugging with GDB==

devkitPro comes with gdb, the gnu debugger, which has been configured to allow remote debugging over the USB Gecko.  You compile a stub of code into your wii program and run the debugger on your pc.  Firstly include the code which establishes the connection:

[[DevkitPro]] comes with gdb, the gnu debugger, which has been configured to allow remote debugging over the [[USBGecko|USB Gecko]].  You compile a stub of code into your wii program and run the debugger on your pc.  Firstly include the code which establishes the connection:

     #include <debug.h>

     #include <debug.h>

Your wii code must be compiled with the option -g linked with the option -ldb, included before other libraries such as -logc.   

Your wii code must be compiled with the option -g linked with the option -ldb, included before other libraries such as -logc.   

Start your wii code using normal means such as the homebrew channel.  Start the more user friendly versino of gdb by typing:

Start your wii code using normal means such as the homebrew channel.  There are three debugging commands available with devkitPro are:

* powerpc-gekko-gdb: the basic text version of gdb driven from the command line

* powerpc-gekko-gdbtui: a version of gdb which includes a text window showing the source code of your application

Assuming that you have started the text based gdb, at the command prompt type:

 

At the gdb command prompt, type:

  target remote /dev/ttyUSB0

  target remote /dev/ttyUSB0