GNOME Bugzilla – Bug 412717
Crash when opening a new tab with window maximized
Last modified: 2007-03-06 16:57:14 UTC
Steps to reproduce: 1. Launch gnome-terminal 2. Maximize the window 3. File -> Open tab or Ctrl+Shift+T Stack trace: $ gdb gnome-terminal GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"... Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /usr/bin/gnome-terminal [Thread debugging using libthread_db enabled] [New Thread -1227150736 (LWP 3143)] [New Thread -1249793136 (LWP 3165)] Program received signal SIGSEGV, Segmentation fault.
+ Trace 114373
Thread NaN (LWP 3143)
The program is running. Exit anyway? (y or n) y Other information: /home/adri2000/packaging/vte/ is where I built the vte packages with debugging symbols. Ubuntu feisty, gnome-terminal 2.17.92-0ubuntu1, vte 1:0.15.4-0ubuntu1.
Ok, this doesn't fall over for me. As the implication is that row == NULL, it would be useful to check the value of screen->cursor_current.row and the contents of *screen->row_data.
(gdb) p row $1 = (VteRowData *) 0x0 (gdb) p screen->cursor_current.row $2 = -1 (gdb) p *screen->row_data $3 = {delta = 0, length = 0, max = 10000, cached_item = -1, cached_data = 0x0, array = 0x842e1e8, free = 0xb7dcae40 <vte_free_row_data>, user_data = 0x0}
Ubuntu bug about that: https://beta.launchpad.net/vte/+bug/88489
*** Bug 412977 has been marked as a duplicate of this bug. ***
This is a recipe that resembles my actual production account: - start with clean profile - open terminal, open three more tabs - gnome-save-session - logout and back in, g-t opens briefly and crashes "gnome-terminal --geometry 130x40" crashes immediately, but I didn't check whether it's the very same crash/root cause.
Created attachment 83534 [details] [review] Ensure we don't set the current.row to -1 This looks like the cause.
Martin, 'gnome-terminal --geometry 130x40' was enough to trigger it for me and that patch does indeed prevent it.
Hmm, along with bug 410534, I think I'll have to plead with Behdad for another brown-paper-bag release! r1776: 2007-02-28 Chris Wilson <chris@chris-wilson.co.uk> Bug 412717 – Crash when opening a new tab with window maximized * src/vte.c (vte_terminal_size_allocate): We didn't carefully check the values we were clamping the cursor to and ended up setting it to -1... Don't do that!
*** Bug 413580 has been marked as a duplicate of this bug. ***
*** Bug 413581 has been marked as a duplicate of this bug. ***
verified fixed
*** Bug 413630 has been marked as a duplicate of this bug. ***
*** Bug 413893 has been marked as a duplicate of this bug. ***
*** Bug 415377 has been marked as a duplicate of this bug. ***