Several useful developer tools have been build around GObject technology. The next sections briefly introduce them and link to the respective project pages. Writing GObjects can be a tedious task. It requires a lot of typing and just doing a copy/paste requires a great deal of care. One obvious idea is to use some sort of templates for the class skeletons. and then run them through a special tool to generate the real C files. GOB/ (or GOB2) is such a tool. It is a preprocessor which can be used to build GObjects with inline C code so that there is no need to edit the generated C code. The syntax is inspired by Java and Yacc or Lex. The implementation is intentionally kept simple: the inline C code provided by the user is not parsed. Yet another tool that you may find helpful when working with GObjects is G-Inspector. It is able to display Glib/Gtk+ objects and their properties. The reference counting scheme used by GObject does solve quite a few memory management problems but also introduces new sources of bugs. In large applications, finding the exact spot where the reference count of an Object is not properly handled can be very difficult. Hopefully, there exist a tool named refdbg/ which can be used to automate the task of tracking down the location of invalid code with regard to reference counting. This application intercepts the reference counting calls and tries to detect invalid behavior. It suports a filter-rule mechanism to let you trace only the objects you are interested in and it can be used together with gdb. g_trap_object_ref Note that if GObject has been compiled with --enable-debug=yes, it exports a trap variable static volatile GObject *g_trap_object_ref; If set to a non-NULL value, g_object_ref() and g_object_unref() will be intercepted when called with that value. The API documentation for most of the Glib, GObject, GTK+ and GNOME libraries is built with a combination of complex tools. Typically, the part of the documentation which describes the behavior of each function is extracted from the specially-formatted source code comments by a tool named gtk-doc which generates docbook xml and merges this docbook xml with a set of master xml docbook files. These xml docbook files are finally processed with xsltproc (a small program part of the libxslt library) to generate the final html output. Other tools can be used to generate pdf output from the source xml. The following code excerpt shows what these comments look like. /** * gtk_widget_freeze_child_notify: * @widget: a #GtkWidget * * Stops emission of "child-notify" signals on @widget. The signals are * queued until gtk_widget_thaw_child_notify() is called on @widget. * * This is the analogue of g_object_freeze_notify() for child properties. **/ void gtk_widget_freeze_child_notify (GtkWidget *widget) { ... The great thoroughful documentation on how to setup and use gtk-doc in your project is provided on the gnome developer website.