[apport] gnome-terminal crashed with SIGSEGV

[feiy]

Binary package hint: gnome-terminal

telnet a suse linux with gbk code and input chinese word use scim

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Mar 30 08:24:02 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-terminal
Package: gnome-terminal 2.18.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-terminal
ProcCwd: /home/feiy
ProcEnviron:
 LANGUAGE=zh_CN:zh:en_US:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/feiy/Programs/Flex2/SDK
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-terminal
Stacktrace:
 #0 0xb7532a00 in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Uname: Linux feiy-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Daniel Holbach (dholbach)]

Thanks for your bug report.

[Apport retracing service (apport)]

StacktraceTop:malloc_consolidate () from /lib/tls/i686/cmov/libc.so.6
_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libfreetype.so.6
?? ()

[Daniel Holbach (dholbach)]

Can you run gnome-terminal under valgrind and attach the log here? http://wiki.ubuntu.com/Valgrind might help with that.

[feiy (eshangrao)]

ok ,i'll install the valgrind to get the debug log

2007/3/30, Daniel Holbach <email address hidden>:
>
> Can you run gnome-terminal under valgrind and attach the log here?
> http://wiki.ubuntu.com/Valgrind might help with that.
>
> ** Changed in: gnome-terminal (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> [apport] gnome-terminal crashed with SIGSEGV
> https://launchpad.net/bugs/98813
>

--
闲云孤鹤 - 清冷香中抱膝吟

[feiy (eshangrao)]

the debug log with the command:

 G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gnome-terminal

in the new gnome-termail window,i login a suse linux 8(GB2312 code),input some chinese word by scim to reproduce the crash

[Sebastien Bacher (seb128)]

did you get the crash during that run? The log has no clear error

[feiy (eshangrao)]

yes!the term is dead,so i kill it!i must upload a log again?

2007/3/31, Sebastien Bacher <email address hidden>:
>
> did you get the crash during that run? The log has no clear error
>
> --
> [apport] gnome-terminal crashed with SIGSEGV
> https://launchpad.net/bugs/98813
>

--
闲云孤鹤 - 清冷香中抱膝吟

[Sebastien Bacher (seb128)]

The log has no error, could you try to get a new one?

[Sebastien Bacher (seb128)]

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.

[Michael Wayne Goodman (goodmami)]

I have been seeing the same symptoms. I was at first unable to reproduce it reliably, but I found that button-mashing (like repeating the home keys: "asdf;lkj") while in unicode-input mode (scim) would crash it quickly. Actually, it doesn't crash, it just locks up. I have to then kill it manually (which kills all other instances of gnome-terminal at the same time).

I tried to follow the valgrind wiki in order to produce this log, but if I did something wrong please let me know. I'm not too skilled at reporting this kind of bug yet, but I'm willing to learn.

Attached is my valgrind log.

also, please reopen this bug, as I need to use unicode from the command line for my school project. I regularly use grep, sed, awk, etc. with unicode, and these lock-ups are a pain

[Sebastien Bacher (seb128)]

The valgrind log has no error. Could you open a new bug rather than comment on a closed one? The issue might be not the same one and the submitter might be not interested in the mails about yours