GNOME Bugzilla – Bug 609462
crash in Terminal: Rapidly hitting 'd' in v...
Last modified: 2010-02-09 21:21:30 UTC
Version: 2.26.2 What were you doing when the application crashed? Rapidly hitting 'd' in vi to delete lines. 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: 151207936 vsize: 151207936 resident: 30736384 share: 4460544 rss: 30736384 rss_rlim: 0 CPU usage: start_time: 1265649680 rtime: 9737 utime: 84110544 stime: 13263103 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-terminal' 10344: gnome-terminal ----------------- lwp# 1 / thread# 1 -------------------- fef028f5 waitid (0, 2f6c, 8047090, 3) feeb2ee5 waitpid (2f6c, 804714c, 0, fed69389) + 65 fed69790 g_spawn_sync (0, 8a6b398, 0, 4, 0, 0) + 418 fed69b90 g_spawn_command_line_sync (85804b8, 0, 0, 0, 804726c) + 5c fad51e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a48f0, 2868, 0, fad51fde) + f3 fad520c2 __1cMcheck_if_gdb6F_v_ (feed82b5, fef80000, 80472ec, feefd2af, b, 0) + 12e fad51a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80473a0) + 64 feefd2af __sighndlr (b, 0, 80473a0, fad51a30) + f feef032f call_user_handler (b) + 2af feef055f sigacthandler (b, 0, 80473a0) + df --- called from signal handler with signal 11 (SIGSEGV) --- faa50d57 _vte_terminal_cleanup_tab_fragments_at_cursor (81c67e0, faadfca4, 4, faa6ebbe) + 127 faa6ec2d vte_sequence_handler_le (81c67e0, 814e790, 1, faa71b8a) + 79 faa71cb5 _vte_terminal_handle_sequence (81c67e0, 81340d0, 4b9, 814e790) + 139 faa52769 vte_terminal_process_incoming (81c67e0, 0) + 3b1 faa640e0 time_process_incoming (81c67e0, 1, 81c67e0, faa64172) + 2c faa64310 process_timeout (0, fedda278, 8047788, fed34b19) + 1ac fed34b2f g_timeout_dispatch (83d59b0, faa64164, 0, 8047800) + 23 fed32d5a g_main_context_dispatch (80c82f8, 0, 895db10, d) + 262 fed333fd g_main_context_iterate (80c82f8, 1, 1, 80a50e8) + 475 fed33a71 g_main_loop_run (83670f8, 83670f8, 80a8000, fe97286e) + 1dd fe972917 gtk_main (8047940, 0, 8100cd4, feffb804, 80479e0, fefdcf60) + b7 0806ad32 main (1, 8047a40, 8047a48, 80479fc) + 8f6 0806701d _start (1, 8047b40, 0, 8047b4f, 8047b9a, 8047bd8) + 7d ----------------- lwp# 2 / thread# 2 -------------------- fef02055 read (14, f62def54, 14) fed34f69 child_watch_helper_thread (0, 8367840, 200, fed5b41e) + 29 fed5b543 g_thread_create_proxy (8367840, fef80000, f62defec, feefcf0e) + 133 feefcf46 _thrp_setup (faf00a00) + 7e feefd1d0 _lwp_start (faf00a00, 0, 0, feefcf0e, 0, 0) ----------- .xsession-errors (514990 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 taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 596460 ***