GNOME Bugzilla – Bug 609351
crash in Terminal: hitting 'x' in vi.
Last modified: 2010-02-08 19:12:19 UTC
Version: 2.26.2 What were you doing when the application crashed? hitting 'x' in vi. Distribution: Solaris Express Community Edition snv_119 X86 Gnome Release: 2.26.3 2009-07-06 (Sun Microsystems, Inc.) BugBuddy Version: 2.26.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10601901 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 162816000 vsize: 162816000 resident: 42418176 share: 4460544 rss: 42418176 rss_rlim: 0 CPU usage: start_time: 1265224308 rtime: 11467 utime: 91727291 stime: 22944832 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 1734: gnome-terminal ----------------- lwp# 1 / thread# 1 -------------------- fef028f5 waitid (0, 2853, 80470a0, 3) feeb2ee5 waitpid (2853, 804715c, 0, fed69389) + 65 fed69790 g_spawn_sync (0, 8e05598, 0, 4, 0, 0) + 418 fed69b90 g_spawn_command_line_sync (950dd28, 0, 0, 0, 804727c) + 5c fad51e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a48f0, 6c6, 0, fad51fde) + f3 fad520c2 __1cMcheck_if_gdb6F_v_ (feed82b5, fef80000, 80472fc, feefd2af, b, 0) + 12e fad51a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80473b0) + 64 feefd2af __sighndlr (b, 0, 80473b0, fad51a30) + f feef032f call_user_handler (b) + 2af feef055f sigacthandler (b, 0, 80473b0) + df --- called from signal handler with signal 11 (SIGSEGV) --- faa50d39 _vte_terminal_cleanup_tab_fragments_at_cursor (8bab108, dcf, faa6ed78, faa510ca) + 109 faa512a6 _vte_terminal_insert_char (8bab108, 79, 0, 0) + 1ea faa52a62 vte_terminal_process_incoming (8bab108, 0) + 6aa faa640e0 time_process_incoming (8bab108, 1, 8bab108, faa64172) + 2c faa64310 process_timeout (0, fedda278, 8047798, fed34b19) + 1ac fed34b2f g_timeout_dispatch (8fb2930, faa64164, 0, 8047810) + 23 fed32d5a g_main_context_dispatch (80c82f8, 0, 8d99858, 14) + 262 fed333fd g_main_context_iterate (80c82f8, 1, 1, 80a50e8) + 475 fed33a71 g_main_loop_run (83670f8, 83670f8, 80a8000, fe97286e) + 1dd fe972917 gtk_main (feffb804, 0, 8100cd4, feffb804, 80479f0, fefdcf60) + b7 0806ad32 main (1, 8047a44, 8047a4c, 8066fbf) + 8f6 0806701d _start (1, 8047b44, 0, 8047b53, 8047b91, 8047bba) + 7d ----------------- lwp# 2 / thread# 2 -------------------- fef02055 read (14, f62def54, 14) fed34f69 child_watch_helper_thread (0, 83683f8, 200, fed5b41e) + 29 fed5b543 g_thread_create_proxy (83683f8, fef80000, f62defec, feefcf0e) + 133 feefcf46 _thrp_setup (faf00a00) + 7e feefd1d0 _lwp_start (faf00a00, 0, 0, feefcf0e, 0, 0) ----------- .xsession-errors (418303 sec old) --------------------- (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:1682): Gtk-WARNING **: About JDS: missing action About JDS ...Too much output, ignoring rest... --------------------------------------------------
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 bug 596460 ***