gnome-terminal crashed with SIGSEGV in strlen()

Bug #121630 reported by Brian J. Murrell
4
Affects Status Importance Assigned to Milestone
GNOME Terminal
Fix Released
Critical
gnome-terminal (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-terminal

I ran gnome-session-save and all of my gnome-terminals disappeared. gnome-terminal segfaulted. I know I've seen this before and thought I had opened a bug on it but I can't seem to find it. now. Maybe launchpad will find it for me with the new duplicate matching code. :-)

ProblemType: Crash
Architecture: i386
Date: Thu Jun 21 16:57:14 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-terminal
NonfreeKernelModules: vmnet vmmon via82cxxx
Package: gnome-terminal 2.18.1-1ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-terminal --geometry=80x50 --tab-with-profile=Default -e ssh-loop\ build --tab-with-profile=Default -e ssh-loop\ orion --tab-with-profile=Default -e ssh-loop\ mountain
ProcCwd: /home/brian
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/brian/bin:/sbin:/bin:/usr/sbin/:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/StarOffice-3.1/linux-x86/bin
 LANG=en_CA.UTF-8
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 vfprintf () from /lib/tls/i686/cmov/libc.so.6
 vasprintf () from /lib/tls/i686/cmov/libc.so.6
 IA__g_vasprintf (string=0xbfd553e4, format=0x80856b0 "%s ",
 IA__g_strdup_vprintf (format=0x80856b0 "%s ",
Title: gnome-terminal crashed with SIGSEGV in strlen()
Uname: Linux pc 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio audio cdrom cdrom dialout dialout dip dip floppy floppy lpadmin mythtv plugdev plugdev scanner scanner video video

Tags: apport-crash
Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Micah Cowan (micahcowan) wrote :

Thanks for your bug report. Please try to obtain a backtrace <http://wiki.ubuntu.com/DebuggingProgramCrash> and attach the file to the bug report (the one that was generated automatically from apport is useless). This will greatly help us in tracking down your problem.

Changed in gnome-terminal:
assignee: nobody → micahcowan
status: New → Incomplete
Revision history for this message
Micah Cowan (micahcowan) wrote :

Never mind; apport's retrace is useless, the one you originally gave with your bug is great.

Revision history for this message
Micah Cowan (micahcowan) wrote :

#10 0xb77789a6 in IA__g_signal_emit_valist (instance=0x80baaa0, signal_id=8,
    detail=0, var_args=0xbfd559b0 "�Yտ\026")
    at /build/buildd/glib2.0-2.13.5/gobject/gsignal.c:2209
...
#11 0xb7778d99 in IA__g_signal_emit (instance=0x80baaa0, signal_id=8,
    detail=0) at /build/buildd/glib2.0-2.13.5/gobject/gsignal.c:2243
 var_args = 0xbfd5599c "\001"

Revision history for this message
Micah Cowan (micahcowan) wrote :

Is ssh-loop some sort of custom script, and what do the arguments {build,orion,mountain} signify?

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote : Re: [Bug 121630] Re: gnome-terminal crashed with SIGSEGV in strlen()

On Thu, 2007-06-21 at 22:13 +0000, Micah Cowan wrote:
> Is ssh-loop some sort of custom script,

Sure:

#!/bin/bash

HOST=$1
shift
while true; do
    ssh -t $HOST "$@"
    echo "hit enter to connect again"
    read a
done

> and what do the arguments
> {build,orion,mountain} signify?

Hostnames.

b.

--
My other computer is your Microsoft Windows server.

Brian J. Murrell

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gnome-terminal:
assignee: micahcowan → desktop-bugs
importance: Undecided → Medium
status: Incomplete → Confirmed
Changed in gnome-terminal:
status: Unknown → New
Changed in gnome-terminal:
status: New → Confirmed
Changed in gnome-terminal:
status: Confirmed → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Fixed upstream, thanks.

Changed in gnome-terminal:
status: Confirmed → Fix Committed
Changed in gnome-terminal:
status: Unknown → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

fixed on hardy, thanks for reporting.

Changed in gnome-terminal:
status: Fix Committed → Fix Released
Changed in gnome-terminal:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.