Version: 2.28.0

What were you doing when the application crashed?
vi /etc/hosts


Distribution:                        OpenSolaris Development snv_125 X86
Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 146755584 vsize: 146755584 resident: 20094976 share: 1675264 rss: 20094976 rss_rlim: 0
CPU usage: start_time: 1257175567 rtime: 21 utime: 164333 stime: 49992 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-terminal'

11796:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3e25 waitid   (0, 2e24, 8046fe0, 3)
 feea3305 waitpid  (2e24, 804709c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 82808f0, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (825de60, 0, 0, 0, 80471bc) + 5c
 fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 2e14, 0, fdaf1ff2) + f3
 fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e
 fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
 feeee825 __sighndlr (b, 0, 80472f8, fdaf1a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 80472f8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd7fce63 _vte_terminal_ring_append (81d4868, 0, 50, fd81f706) + 1f
 fd81f81d vte_sequence_handler_cd (81d4760, 0, 80475a8, fd822112) + 125
 fd822178 vte_sequence_handler_erase_in_display (81d4760, 827bb30, f, fd82376a) + 74
 fd823895 _vte_terminal_handle_sequence (81d4760, 81d0eb0, 507, 827bb30) + 139
 fd802d99 vte_terminal_process_incoming (81d4760, 0) + 405
 fd81481c time_process_incoming (81d4760, 1, 81d4760, fd814ef6) + 2c
 fd81509b update_timeout (0, fedcc460, 8047748, fed26c71) + 1b3
 fed26c87 g_timeout_dispatch (827b5b0, fd814ee8, 0, 80477c0) + 23
 fed24eee g_main_context_dispatch (80cbe38, 78, 81146f8, a) + 262
 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (825a488, 825a488, 80a9800, fe37e73a) + 1dd
 fe37e7e3 gtk_main (3, 0, 80aa0fc, feffb804, 80479a0, fefdcf48) + b7
 0806b594 main     (1, 80479f8, 8047a00, 80479ec) + 944
 080677fd _start   (1, 8047b08, 0, 8047b17, 8047b63, 8047ba7) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef35c5 read     (15, f5cbef50, 14)
 fed270c1 child_watch_helper_thread (0, 8254a88, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8254a88, fef81000, f5cbefe8, feeee45e) + 133
 feeee4b3 _thrp_setup (fdcb0a00) + 9b
 feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)


----------- .xsession-errors (630102 sec old) ---------------------
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 &
...Too much output, ignoring rest...
--------------------------------------------------