Using GDB


	Log In \| Not a Member?	Contact ADC

How to use GDB

Useful GDB Commands

Additional Notes & Comments

GDB allows you to see what your application is doing programmatically while it runs. GDB can be an invaluable tool to trace the execution of an application in order to find the cause of an encountered problem, and to let developers know where their code is failing.

This Note is directed at quality assurance engineers who do not have any experience with GDB.

How to use GDB

You can only use GDB in a UNIX-style environment. For our purposes this means Mac OS X or Mac OS X Server.

You must know the path of the application you are going to debug. As an example, we will use the fictitious application located at: /System/Applications/Foo.app

Foo.app is actually a bundle, or a folder that contains the binary executable as well as the resources for the application. GDB will see the above path as a folder, rather than an executable, thus in the above example, the actual executable is located at: /System/Applications/Foo.app/Foo

Launching an application from GDB

Open a terminal window by selecting Terminal from the Apple menu on Mac OS X Server
or from the Dock on Mac OS X.
Type 'gdb' followed by the path of the application.
For example: "gdb /System/Applications/Foo.app/Foo"
GDB will launch and pause execution when the application is loaded.
To run the application enter 'r'.
Switch to the application and use it normally until you encounter a problem.
Switch back to the Terminal window.

Useful GDB Commands

Here is a list of a few GDB commands you will find extremely useful while doing quality assurance.

STACK BACKTRACE At the prompt you may enter 'bt' to see the last few instructions the application executed. This is called a stack backtrace. You can copy the backtrace from the terminal and paste it into a text document. Stack back traces contain useful debugging information and should be included with your bug report.

PAUSE It is possible to pause execution of an application from the GDB terminal by hitting both the control and c keys. You can then capture a stack backtrace.

CONTINUE To continue execution, enter 'c' at the GDB prompt.

KILL To kill a process, enter 'k' from the GDB prompt.

QUIT You may quit GDB by typing 'q' from the GDB prompt.

HELP GDB has fairly extensive help information on the many other debugger commands available. Type help at the GDB prompt to access this information.

Additional Notes & Comments

It is always good practice to leave the Console window open, either by selecting it from the Tools menu in Workspace Manager, or by the key combination <command-shift-C>. Error messages are often directed to the Console.

You should always include a stack backtrace with any crashing bug report.

It is possible to debug an application from a remote computer through a telnet session.

Programmer oriented resources