Version: 2.28.0

What were you doing when the application crashed?
resizing the terminal window and then it died!


Distribution:                        OpenSolaris Development snv_126 X86
Gnome Release: 2.28.0 2009-10-13 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

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

Memory status: size: 155099136 vsize: 155099136 resident: 28037120 share: 884736 rss: 28037120 rss_rlim: 0
CPU usage: start_time: 1257930176 rtime: 17348 utime: 139885356 stime: 33601956 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

1274:	gnome-terminal --title ECC JumpOff -x ssh -l nbehrens 213.46.228.11
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, 4b9c, 8046fe0, 3)
 feea3305 waitpid  (4b9c, 804709c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 8753be8, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (8709bb8, 0, 0, 0, 80471bc) + 5c
 fdae1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58d0, 4fa, 0, fdae1ff2) + f3
 fdae20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e
 fdae1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
 feeee735 __sighndlr (b, 0, 80472f8, fdae1a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 80472f8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd7dce63 _vte_terminal_ring_append (8723910, 0, 54, fd7ff706) + 1f
 fd7ff81d vte_sequence_handler_cd (8723808, 0, 80475a8, fd802112) + 125
 fd802178 vte_sequence_handler_erase_in_display (8723808, 8282fd0, f, fd80376a) + 74
 fd803895 _vte_terminal_handle_sequence (8723808, 81d1f48, 507, 8282fd0) + 139
 fd7e2d99 vte_terminal_process_incoming (8723808, 0) + 405
 fd7f481c time_process_incoming (8723808, 1, 8723808, fd7f4c62) + 2c
 fd7f4dd3 update_repeat_timeout (0, fedcc460, 8047748, fed26c71) + 17f
 fed26c87 g_timeout_dispatch (8928cb0, fd7f4c54, 0, 80477c0) + 23
 fed24eee g_main_context_dispatch (80cbe38, c8, 82f5e18, 19) + 262
 fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (80a57b0, 80a57b0, 80a9800, fe37e726) + 1dd
 fe37e7cf gtk_main (feffb804, 0, 81198dc, feffb804, 80479a0, fefdcf48) + b7
 0806b594 main     (1, 80479f4, 8047a18, 806779f) + 944
 080677fd _start   (8, 8047b1c, 0, 0, 8047b3f, 8047b42) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (15, f5caef50, 14)
 fed270c1 child_watch_helper_thread (0, 8254c98, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8254c98, fef81000, f5caefe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fdca0a00) + 9b
 feeee650 _lwp_start (fdca0a00, 0, 0, 0, 0, 0)


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