What were you doing when the application crashed?
eclipse visual editor


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 869 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
FG: canHandleContent application/x-unknown-content-type)
FG: _shouldIntercept(application/x-unknown-content-type)
Xlib: unexpected async reply (sequence 0x1c)!
** (nautilus:3762): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
** (bug-buddy:6572): WARNING **: 无法为 打开文件夹 载入图标
--------------------------------------------------

Memory status: size: 110960640 vsize: 0 resident: 110960640 share: 0 rss: 24993792 rss_rlim: 0
CPU usage: start_time: 1162598224 rtime: 0 utime: 3026 stime: 0 cutime:2723 cstime: 0 timeout: 303 it_real_value: 0 frequency: 0

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

(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 -1208509696 (LWP 3762)]
(no debugging symbols found)
0x0059e402 in __kernel_vsyscall ()

+ Trace 82156