 | Services - tools - models - for embedded software development |
|---|
| Services - tools - models - for embedded software development |
|---|
 |  | |
To test performance of the GDB server, a GDB script is used with a
small program (in sw/test-progs/perf.c) which
exercises the model by computing Ackermann's function [1] [2]. This
is driven by a GDB script in
sw/test-progs/gdb-script. This script sets a
breakpoint on the entry point to a, which computes
Ackermann's function. It then carries out the following tests:
Continues past the breakpoint 50 times. This tests the efficiency of running to a breakpoint.
Disassembles the function 5 times. This tests the efficiency of memory access.
Prints the CPU configuration register 10 times. This tests the efficiency of SPR access.
GDB is run in silent batch mode:
or32-uclinux-gdb -batch -batch-silent --command gdb-script
The output is completely suppressed, removing any client I/O overhead. To measure the client's speed of loading (a measure of both model and memory access efficiency), the "Hello World" program from Section 4.5.1 is loaded manually.
| |  | |
| Chapter 5. Optimizing the GDB Server |  | 5.1.1. Load Generated by Debugging Commands |