Changes between Version 5 and Version 6 of Tools/Gdb Server
- Timestamp:
- Feb 25, 2008, 6:43:34 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tools/Gdb Server
v5 v6 6 6 == Overview == 7 7 8 The !GdbServer is able to manage all processors in a soclib platform. Once added to the platform netlist, it listens for TCP connection from [http://www.gnu.org/software/gdb/ Gnu GDB] clients. Once connected, clients can be used to freeze, run, step every processor in the platform, add breakpoints, catch exceptions and dump registers and memory content.8 The !GdbServer is able to manage all processors in a soclib platform. It listens for TCP connection from [http://www.gnu.org/software/gdb/ Gnu GDB] clients. Once connected, clients can be used to freeze, run, step every processor in the platform, add breakpoints, catch exceptions and dump registers and memory content. 9 9 10 10 == Implementation == 11 11 12 The !GdbServer contains no processor specific code and can be used to manage any Soclib processor model using the generic Iss interface. It is implemented as an Iss wrapper class. When the !GdbServer is in use, it intercepts all events between the processor Iss model and the Soclib platform. This enables the !GdbServer to access platform ressources as viewed from the processor without modifing platform components or processor model source code. The !GdbServer is able to freeze the nested processor model while the platform is still running. 12 The !GdbServer contains no processor specific code and can be used to manage any Soclib processor model using the generic Iss interface. It is implemented as an Iss wrapper class. When the !GdbServer is in use, it intercepts all events between the processor Iss model and the Soclib platform. This enables the !GdbServer to access platform ressources as viewed from the processor without modifing platform components or processor model source code. The !GdbServer is able to freeze the wrapped processor model while the platform is still running. 13 14 In order to simpfify the debug in a multi-processor context, all processors wrapped in a !GdbServer will be frozen when a breakpoint is detected in one single processor. 13 15 14 16 == Usage ==