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 599157 - crash in Terminal: resising gnome-terminal
crash in Terminal: resising gnome-terminal
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-21 10:20 UTC by Chavdar Ivanov
Modified: 2009-10-21 14:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Chavdar Ivanov 2009-10-21 10:20:45 UTC
Version: 2.28.0

What were you doing when the application crashed?
resising gnome-terminal


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: 88469504 vsize: 88469504 resident: 18653184 share: 4313088 rss: 18653184 rss_rlim: 0
CPU usage: start_time: 1253527793 rtime: 629 utime: 5273690 stime: 1023575 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

4712:	gnome-terminal -x /bin/ksh
-----------------  lwp# 1 / thread# 1  --------------------
 d12f3e25 waitid   (0, 134c, 80468a0, 3)
 d12a3305 waitpid  (134c, 804695c, 0, d115b60d) + 65
 d115ba14 g_spawn_sync (0, 82ca850, 0, 4, 0, 0) + 418
 d115be28 g_spawn_command_line_sync (82cbda0, 0, 0, 0, 8046a7c) + 5c
 d0481e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a6060, 1268, 0, d0481ff2) + f3
 d04820d6 __1cMcheck_if_gdb6F_v_ (d1381000, d1381000, 8046b04, d12ee825, b, 0) + 12e
 d0481a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046bb8, d10c2a00, d1381000, 8046b74) + 64
 d12ee825 __sighndlr (b, 0, 8046bb8, d0481a30) + 15
 d12e15ef call_user_handler (b) + 2af
 d12e181f sigacthandler (b, 0, 8046bb8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 d018ce63 _vte_terminal_ring_append (81cb0f0, 0, 51, d01af706) + 1f
 d01af81d vte_sequence_handler_cd (81cafe8, 0, 8046e68, d01b2112) + 125
 d01b2178 vte_sequence_handler_erase_in_display (81cafe8, 82c9400, f, d01b376a) + 74
 d01b3895 _vte_terminal_handle_sequence (81cafe8, 81d3848, 50c, 82c9400) + 139
 d0192d99 vte_terminal_process_incoming (81cafe8, 40630000) + 405
 d01a481c time_process_incoming (81cafe8, 1, 81cafe8, d01a4ef6) + 2c
 d01a509b update_timeout (0, d11cc460, 8047008, d1126c71) + 1b3
 d1126c87 g_timeout_dispatch (8294ca8, d01a4ee8, 0, 8047080) + 23
 d1124eee g_main_context_dispatch (80ca938, 78, 826da10, b) + 262
 d112559f g_main_context_iterate (80ca938, 1, 1, 80a6828) + 483
 d1125bc9 g_main_loop_run (80a5f58, 80a5f58, 80a9800, d0dae73a) + 1dd
 d0dae7e3 gtk_main (d13d5e56, 0, 80aa134, d13fc804, 8047260, d13ddf48) + b7
 0806b594 main     (1, 80472bc, 80472cc, d13fc804) + 944
 080677fd _start   (3, 80473e8, 80473f7, 80473fa, 0, 8047403) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 d12f35c5 read     (14, cba9ef50, 14)
 d11270c1 child_watch_helper_thread (0, 80b2f30, 200, d114d1de) + 29
 d114d303 g_thread_create_proxy (80b2f30, d1381000, cba9efe8, d12ee45e) + 133
 d12ee4b3 _thrp_setup (d0640a00) + 9b
 d12ee740 _lwp_start (d0640a00, 0, 0, 0, 0, 0)
Comment 1 Christian Persch 2009-10-21 14:20:19 UTC

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