1 This is bug-buddy, a graphical bug reporting tool.
6 bug-buddy can extract debugging information from a crashed application and
7 create either a stacktrace or a minidump file to send to the GNOME
13 bug-buddy uses gdb to collect the stacktrace from the crashed application.
14 It ships a GTK+ module, called gnomesegvhandler, that allows bug-buddy to
15 come up automatically every time a GTK+ application crashes.
20 It shouldn't be harder than the usual
22 ~$ ./configure --prefix=/your/prefix
26 but there are some things that might be tricky: the gnomebreakpad module
27 should be installed in your GTK+ modules directory (default is
28 /usr/lib/gtk-2.0/modules), and GTK+ itself should be told to load that module
29 every time an application starts.
31 There are two ways to do that:
32 - add "gnomesegvhandler" to the GTK_MODULES environment variable (this is how it
33 works in GNOME 2.22 and older, as gnome-session takes care of setting the
34 variable at startup); this is now deprecated.
35 - add a boolean "/apps/gnome_settings_daemon/gtk-modules/gnomesegvhandler" GConf
36 key (requires GTK+ 2.14.2 and gnome-settings-daemon 2.24.0 to work properly).
37 The key is installed by default by bug-buddy, and this method is the
38 reccomended for GNOME 2.24 or newer.
40 So, if gnomebreakpad for some reason doesn't seem to work, check the GConf key
41 or the GTK_MODULES environment variable.
46 A bug reporting tool can have bugs as well, funny isn't it? :-P
47 Please report your bugs to the GNOME bug tracking system
48 (http://bugzilla.gnome.org), under the bug-buddy component.
50 Jacob Berkman <jberkman@andrew.cmu.edu>
51 Fernando Herrera <fherrera@novell.com>
52 Cosimo Cecchi <cosimoc@gnome.org>