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 155700 - gnome terminal crash when displaying Chinese characters
gnome terminal crash when displaying Chinese characters
Status: RESOLVED INCOMPLETE
Product: gnome-terminal
Classification: Core
Component: general
1.9.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-10-18 08:26 UTC by xuq
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description xuq 2004-10-18 08:26:44 UTC
Distribution: Debian testing/unstable
Package: gnome-terminal
Severity: normal
Version: GNOME2.8.1 2.7.3
Gnome-Distributor: Ubuntu
Synopsis: gnome terminal crash when displaying Chinese characters
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.7.3
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:

Steps to reproduce the crash:
1. Display some Chinese charactors in the terminal, for example telnet a
Chinese BBS, or ls a folder containing Chinese file names.
2. Move the mouse within the terminal window
3. 

Expected Results:
crash. The gnome terminal will not crash as long as the the mouse is not
moved.

How often does this happen?
every time when mouse was moved.

Additional Information:
I use a Windows font: simsun.ttf


Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 1088305760 (LWP 5357)]
[New Thread 1115937712 (LWP 5360)]
[Thread debugging using libthread_db enabled]
[New Thread 1088305760 (LWP 5357)]
[New Thread 1115937712 (LWP 5360)]
(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread 1088305760 (LWP 5357)]
[New Thread 1115937712 (LWP 5360)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #7 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #12 ??
  • #13 ??
  • #14 g_realloc
    from /usr/lib/libglib-2.0.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-18 04:26 -------


Unknown version 2.7.3 in product gnome-terminal. Setting version to "1.9.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was xuq@tsinghua.edu.cn.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Caleb Groom 2004-10-18 22:54:09 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Please make sure that the package was
compiled with debugging symbols and see
http://bugzilla.gnome.org/getting-traces.cgi for more information about useful
stack traces.