Most recent edit on 2006-01-30 08:28:33 by a194-109-198-99.adsl.xs4all.nl
Additions:
5. Debug
Deletions:
5. Debug
Edited on 2006-01-30 08:28:10 by a194-109-198-99.adsl.xs4all.nl [English]
Additions:
5. Debug
Now Skyeye supports the RDI (remote debug interface) protocol of GDB. In the future, we hope SkyEye can support more debugging protocols.
5.1 gdb debugging
In this section we will give some step by step instructions for debugging your kernel image using gdb RDI. RDI function in SkyEye is not completed yet, so you may encounter some problems. We will finish it soon.
Firstly you should have a gdb for your target installed on your host machine; there should be a binary called something like arm-elf-gdb. This gdb will be used to communicate with SkyEye to get detailed debug infomation. If you have ever used gdbserver, this will be familiar. SkyEye is just like your gdbserver in usage.
You can load your image on SkyEye with -d option to turn on debugging. Please refer to ?.
When Skyeye is launched, it will stop at the address of the first instruction of your image. Then run the gdb for your target in another terminal (using for instance X11 to open multiple terminal windows).
At this time, gdb side will show the current PC (program counter), and some running infomation of your image. Then you can run gdb commands to debug your image.
Deletions:
5. Debug
Now Skyeye supports RDI(remote debug interface) protocal of GDB. In the future, we hope SkyEye can support more debug protocal .
* 5.1 gdb debugging
In this section we will give you some instruction step by step to debug your image on kernel by gdb RDI.Now RDI function in SkyEye is not completed.So you maybe encounter some problems. We will finish it as soon as fast.
Firstly you should have gdb for your target in your host machine such arm-elf-gdb or some others. It will be used to communicate with SkyEye to get detailed debug infomation. If you have ever used gdbserver, that is good. SkyEye just like your gdbserver in usage.
Then you can run your image on SkyEye with -d option. Please refer to
When Skyeye is launched, it will stop at address of the first instruction of your image. Then run gdb of your target in another terminal. Here I recommend you can use linux GUI to open mutilple console windows.
At this time , gdb side will show current pc , and some running infomation of your image. Then you can run gdb commands to debug your image.
Edited on 2005-12-12 20:43:24 by 137.71.23.54
Additions:
5. Debug
Now Skyeye supports RDI(remote debug interface) protocal of GDB. In the future, we hope SkyEye can support more debug protocal .
* 5.1 gdb debugging
In this section we will give you some instruction step by step to debug your image on kernel by gdb RDI.Now RDI function in SkyEye is not completed.So you maybe encounter some problems. We will finish it as soon as fast.
Firstly you should have gdb for your target in your host machine such arm-elf-gdb or some others. It will be used to communicate with SkyEye to get detailed debug infomation. If you have ever used gdbserver, that is good. SkyEye just like your gdbserver in usage.
Then you can run your image on SkyEye with -d option. Please refer to
When Skyeye is launched, it will stop at address of the first instruction of your image. Then run gdb of your target in another terminal. Here I recommend you can use linux GUI to open mutilple console windows.
./arm-elf-gdb imagename
Then run the following command under gdb prompt:
target remote :12345
At this time , gdb side will show current pc , and some running infomation of your image. Then you can run gdb commands to debug your image.
Deletions:
TODO
Oldest known version of this page was edited on 2005-12-02 21:18:22 by 137.71.23.54 []
Page view:
TODO
Page was generated in 0.1264 seconds