GNOME Bugzilla – Bug 599024
crash in Terminal: Hit enter to input a com...
Last modified: 2009-10-20 11:22:21 UTC
Version: 2.28.0 What were you doing when the application crashed? Hit enter to input a command. Distribution: Solaris Express Community Edition snv_125 X86 Gnome Release: 2.28.0 2009-09-28 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10603000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 149712896 vsize: 149712896 resident: 22515712 share: 4677632 rss: 22515712 rss_rlim: 0 CPU usage: start_time: 1256029120 rtime: 20 utime: 158316 stime: 46061 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 1323: gnome-terminal ----------------- lwp# 1 / thread# 1 -------------------- feef3e25 waitid (0, 532, 8046520, 3) feea3305 waitpid (532, 80465dc, 0, fed5b60d) + 65 fed5ba14 g_spawn_sync (0, 828e928, 0, 4, 0, 0) + 418 fed5be28 g_spawn_command_line_sync (81255b8, 0, 0, 0, 80466fc) + 5c fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58d0, 52b, 0, fdaf1ff2) + f3 fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046784, feeee825, b, 0) + 12e fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046838, fecc2a00, fef81000, 80467f4) + 64 feeee825 __sighndlr (b, 0, 8046838, fdaf1a30) + 15 feee15ef call_user_handler (b) + 2af feee181f sigacthandler (b, 0, 8046838) + df --- called from signal handler with signal 11 (SIGSEGV) --- fd7ece63 _vte_terminal_ring_append (81d90f0, 0, 50, fd80f706) + 1f fd80f81d vte_sequence_handler_cd (81d8fe8, 0, fd7c0018, fd812112) + 125 fd812178 vte_sequence_handler_erase_in_display (81d8fe8, 81318c0, f, fd81376a) + 74 fd813895 _vte_terminal_handle_sequence (81d8fe8, 81e1a38, 50b, 81318c0) + 139 fd7f2d99 vte_terminal_process_incoming (81d8fe8, 0) + 405 fd80481c time_process_incoming (81d8fe8, 1, 81d8fe8, fd804ef6) + 2c fd80509b update_timeout (0, fedcc460, 8046c88, fed26c71) + 1b3 fed26c87 g_timeout_dispatch (828da08, fd804ee8, 0, 8046d00) + 23 fed24eee g_main_context_dispatch (80d22e0, 78, 826ac38, a) + 262 fed2559f g_main_context_iterate (80d22e0, 1, 1, 80a6858) + 483 fed25bc9 g_main_loop_run (80a57e0, 80a57e0, 80a9800, fe37e73a) + 1dd fe37e7e3 gtk_main (fefd4e56, 0, 80aa184, feffb804, 8046ee0, fefdcf48) + b7 0806b594 main (1, 8046f3c, 8046f44, feffb804) + 944 080677fd _start (1, 8047084, 0, 8047093, 80470eb, 80470f8) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feef35c5 read (15, f58bef50, 14) fed270c1 child_watch_helper_thread (0, 80b3770, 200, fed4d1de) + 29 fed4d303 g_thread_create_proxy (80b3770, fef81000, f58befe8, feeee45e) + 133 feeee4b3 _thrp_setup (fdcb0a00) + 9b feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)
*** This bug has been marked as a duplicate of bug 596460 ***