Version: 2.2.3

What were you doing when the application crashed?
I was editing 3 small source code files. Then I checked the Debug plugin and the app crashed.


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.12-1-386 #1 Tue Sep 27 12:41:08 JST 2005 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 34516992 vsize: 34516992 resident: 17907712 share: 10739712 rss: 17907712 rss_rlim: 4294967295
CPU usage: start_time: 1202557336 rtime: 2413 utime: 2236 stime: 177 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/anjuta'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f126b0 (LWP 5421)]
(no debugging symbols found)
0xb74e12fe in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 188646

----------- .xsession-errors (9 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Error (18381): Bad dynamic code table in flate stream
Error (18381): Bad block header in flate stream
Error (17672): Unexpected end of file in flate stream
** Message: Spawning script
(anjuta:5421): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed
(anjuta:5421): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(anjuta:5421): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
(bug-buddy:5776): gnome-vfs-modules-WARNING **: Could not initialize inotify
--------------------------------------------------