gdb gdbserver arm程序调试（gdb gdbserver arm程序调试）.doc

gdb+gdbserver arm程序调试(gdb + gdbserver arm程序调试)
Content remote debugging environment consists of host GDB and target debugging stub, both of which are connected by serial port or TCP. Using the GDB standard serial protocol to work together, the monitoring and debugging functions of the system kernel and upper application are realized. Debugging stub is a piece of code in embedded systems that exists as a medium between the host GDB and the target debugger. For now, the embedded Linux system, there are mainly three kinds of remote debugging methods, which are suitable for different occasions with ROM Monitor debugging: debug target program, debugging system and debugging kernel in KGDB user space program with gdbserver. The difference between the three debugging methods lies in the difference in the form of remote debugging of stub by the target machine, while the design idea and implementation method are approximately the same. And the mon thing we do is debug applications. Gdb+gdbserver is used to debug. In many cases, users need to debug an application repeatedly, plex programs. Using GDB method debugging, because the embedded system resources are limited, can not be directly on the target system debugging, usually using gdb+gdbserver way debugging.
Simple use of GDB and gdb+gdbserver mode for ARM program
The simple use of GDB
GDB is a powerful program debugging tool released by GNU open anization under UNIX. Maybe you love that way of a graphical interface, like VC, BCB and IDE debugging, but if you do the software under the UNIX platform, you will find the GDB
debugging tools have more powerful than graphical debugger VC, BCB function. The so-called "Sometimes an inch may prove long. is the truth, everyone has his own advantages.". In general, GDB mainly helps plete the following four aspects of function: 1, start your program, you can according to your own custom requirements run the program as you please.
2. Allow the debugged program to stop at the brea