After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 598465 - crash in Terminal: running zsh
crash in Terminal: running zsh
Status: RESOLVED DUPLICATE of bug 596460
Product: vte
Classification: Core
Component: general
0.22.x
Other All
: Normal critical
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-14 16:44 UTC by sam.cramer
Modified: 2009-10-15 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description sam.cramer 2009-10-14 16:44:08 UTC
Version: 2.28.0

What were you doing when the application crashed?
running zsh


Distribution:                 Solaris Express Community Edition snv_nightly 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: 142348288 vsize: 142348288 resident: 19570688 share: 1232896 rss: 19570688 rss_rlim: 0
CPU usage: start_time: 1255538609 rtime: 24 utime: 208389 stime: 37607 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

6858:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3377 waitid   (0, 1ace, 8046800, 3)
 feea32f5 waitpid  (1ace, 80468bc, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 8291900, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (81bae38, 0, 0, 0, 80469dc) + 5c
 fe071e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a6030, 1aca, 0, fe071ff2) + f3
 fe0720d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046a64, feeee805, b, 0) + 12e
 fe071a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046b18, fecc2a00, fef81000, 8046ad4) + 64
 feeee805 __sighndlr (b, 0, 8046b18, fe071a30) + 15
 feee15df call_user_handler (b) + 2af
 feee180f sigacthandler (b, 0, 8046b18) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fdd7ce63 _vte_terminal_ring_append (81ce0f0, 0, 50, fdd9f706) + 1f
 fdd9f81d vte_sequence_handler_cd (81cdfe8, 0, 8046dc8, fdda2112) + 125
 fdda2178 vte_sequence_handler_erase_in_display (81cdfe8, 828e840, f, fdda376a) + 74
 fdda3895 _vte_terminal_handle_sequence (81cdfe8, 81d7c68, 50c, 828e840) + 139
 fdd82d99 vte_terminal_process_incoming (81cdfe8, 0) + 405
 fdd9481c time_process_incoming (81cdfe8, 1, 81cdfe8, fdd948ae) + 2c
 fdd94a4c process_timeout (0, fedcc460, 8046f68, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (81f39c0, fdd948a0, 0, 8046fe0) + 23
 fed24eee g_main_context_dispatch (80ce9c8, 0, 8270998, b) + 262
 fed2559f g_main_context_iterate (80ce9c8, 1, 1, 80a6828) + 483
 fed25bc9 g_main_loop_run (8255c58, 8255c58, 80a9800, fe97e73a) + 1dd
 fe97e7e3 gtk_main (feffb804, 0, 80aa2f4, feffb804, 80471c0, fefdcf48) + b7
 0806b594 main     (1, 8047214, 804721c, 806779f) + 944
 080677fd _start   (1, 804733c, 0, 804734b, 8047391, 80473c5) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef2ea7 read     (14, f83fef50, 14)
 fed270c1 child_watch_helper_thread (0, 80b2f70, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (80b2f70, fef81000, f83fefe8, feeee44e) + 133
 feeee4a3 _thrp_setup (fe230a00) + 9b
 feeee730 _lwp_start (fe230a00, 0, 0, 0, 0, 0)
Comment 1 Akhil Laddha 2009-10-15 02:58:57 UTC
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 598458 ***
Comment 2 Christian Persch 2009-10-15 23:05:45 UTC

*** This bug has been marked as a duplicate of bug 596460 ***