GNOME Bugzilla – Bug 395786
crash in Terminal:
Last modified: 2007-01-13 03:12:00 UTC
Version: 2.16.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.17.5 2007-01-10 (FreeBSD GNOME Project) BugBuddy Version: 2.17.3 System: FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Jan 5 09:52:54 CST 2007 root@govinda.dot:/usr/obj/usr/src/sys/GOVINDA amd64 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled Memory status: size: 118548 vsize: 118548 resident: 18584 share: 76660124 rss: 18584 rss_rlim: 4646 CPU usage: start_time: 409266713 rtime: 0 utime: 35 stime: 2901927 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/bin/gnome-terminal' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100091] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100091] 0x0000000805b45dba in wait4 () from /lib/libc.so.7
+ Trace 101555
----------- .xsession-errors --------------------- streamtuner: SHOUTcast: parse error at shoutcast.c:695 warning: Unable to get location for thread creation breakpoint: generic error /usr/local/share/gnome/bug-buddy/gdb-cmd:2: Error in sourced command file: Backtrace limit of 200 exceeded (bug-buddy:54855): GLib-GObject-WARNING **: invalid uninstantiatable type `event' in cast to `GObject' GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed aborting... LibGTop-Server: pid 54856 received eof. warning: Unable to get location for thread creation breakpoint: generic error /usr/local/share/gnome/bug-buddy/gdb-cmd:2: Error in sourced command file: Backtrace limit of 200 exceeded --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 395784 ***