Intel(r) UEFI Development Kit Debugger Tool User Manual

7.4.3 End the GDB debug session
To end a GDB debug session, follow these steps:
1. Halt the TARGET if the TARGET is running
2. In GDB, enter the quit command to end the debugging session.
(gdb) quit
A debugging session is active.
Inferior 1 [Remote target] will be detached.
Quit anyway (y or n) y
qTStatus: Remote connection closed
user@user-Ubuntu11-64:~$
Figure 7-5—Detach in GDB
Note: Closing GDB without running the “quit” command leaves
the TARGET firmware in an intermediate state and it cannot
be reattached until restarted.
7.5 Basic GDB debugging operations
The Intel UDK Debugger Tool supports GDB operations for Linux platforms, including
these critical operations:
Embed a breakpoint in the source code. Adding the CpuBreakpoint() statement to
the source code allows the GDB to enter interactive mode when the target executes
the line.
Add a function breakpoint in a debug session. As long as a module’s symbol file
is loaded, use of the break command to set a breakpoint for a function within the
module is permissible. Command syntax for the break command is:
break
In the following example, a breakpoint is added to the IoBitFieldRead16 function:
foo@foo:~$ break IoBitFieldRead16
7.5.1 GDB extension commands
Intel provides several extension commands for GDB on Linux platforms. The following
extension commands add functionality to GDB to support debugging of the target firmware.
Once the commands are loaded, the commands become part of GDB.
Note: Remember that compiler optimization is typically enabled by default. To see more
debug information in the output file, disable compiler optimization for the module
being debugged.
40