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 139441 - [escape_string] gnome-terminal 2.6.0 crashes under chinese locale when starting vim in it
[escape_string] gnome-terminal 2.6.0 crashes under chinese locale when starti...
Status: RESOLVED DUPLICATE of bug 139030
Product: gnome-terminal
Classification: Core
Component: general
2.6.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 139094 140578 141368 142384 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-04-08 03:34 UTC by Joe Cai
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: 2.6.next
GNOME version: 2.5/2.6

Attachments
correct string, in UTF-8 (73 bytes, text/plain)
2004-04-08 08:26 UTC, Mariano Suárez-Alvarez 		Details

Description Joe Cai 2004-04-08 03:34:16 UTC 
Description of Problem:
Gnome-Terminal 2.6.0 crashes under locale
zh_CN.GBK when starting vim in it.

Steps to reproduce the problem:
1. use locale zh_CN.GBK to start gnome
2. start gnome-terminal
3. start vim in gnome-terminal

Actual Results:
gnome-terminal crashes

Expected Results:
no error,no crash

How often does this happen? 
every time

Additional Information:
I use debian sid,kernel 2.6.4-1-k7,the gnome 2.6.0
was built using garnome 2.6.0
Comment 1 Wang WenRui 2004-04-08 05:57:15 UTC 
same problem here, but not every time

and when it crashes:
(gnome-terminal:4411): Gdk-CRITICAL **: file gdkgc.c: line 465
(gdk_gc_get_colormap): assertion `GDK_IS_GC (gc)' failed

(process:4411): GLib-CRITICAL (recursed) **: file gstring.c: line 672
(g_string_erase): assertion `pos >= 0' failed
aborting...
Comment 2 Wang WenRui 2004-04-08 06:37:31 UTC 
stack trace:

+ Trace 45832

  • #0 g_string_erase
    at gstring.c line 672
  • #1 escape_string
    at gmessages.c line 795
  • #2 g_log_default_handler
    at gmessages.c line 888
  • #3 g_logv
    at gmessages.c line 503
  • #4 g_log
    at gmessages.c line 541
  • #5 vte_terminal_handle_sequence
    at vte.c line 6659
  • #6 vte_terminal_process_incoming
    at vte.c line 7112
  • #7 g_timeout_dispatch
    at gmain.c line 3250
  • #8 g_main_dispatch
    at gmain.c line 1895
  • #9 g_main_context_dispatch
    at gmain.c line 2441
  • #10 g_main_context_iterate
    at gmain.c line 2522
  • #11 g_main_loop_run
    at gmain.c line 2726
  • #12 gtk_main
    at gtkmain.c line 1172
  • #13 main
    at terminal.c line 1669 






Comment 3


Wang WenRui





          2004-04-08 07:06:16 UTC
        



this bug may be related to bug#131218






Comment 4


Mariano Suárez-Alvarez





          2004-04-08 07:08:41 UTC
        



Yes it is. I'm in the middle of a gdb session looking at it in fact ;)






Comment 5


Mariano Suárez-Alvarez





          2004-04-08 08:24:04 UTC
        



I get this to happen almost all times; the rest, I see things like

** (gnome-terminal:7844): WARNING **:
\xd8\xd6\xc6\xd7\xd6?\xd0\xf2\xc1\xd0С\x64device-control-string\xb1\xb5\xc4?\xc0\xed
\xb3\xcc\xd0\xf2\xceδ\xa8\xd2\xe5塣

The correct string (without the header) is

控制字符序列“device-control-string”的处理程序未定义。

Marking as a dup of 131218, as this is glib's gmessage.c:escape_string at work.


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






Comment 6


Mariano Suárez-Alvarez





          2004-04-08 08:25:26 UTC
        



Attaching the string, to protect it from Bugzilla's evil hands...






Comment 7


Mariano Suárez-Alvarez





          2004-04-08 08:26:47 UTC
        



Created attachment 26459 [details]
correct string, in UTF-8






Comment 8


Owen Taylor





          2004-04-08 11:39:50 UTC
        



More precisely, it's a duplicate of bug 139030






Comment 9


Owen Taylor





          2004-04-08 11:40:46 UTC
        




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






Comment 10


Mariano Suárez-Alvarez





          2004-04-09 02:14:18 UTC
        



See bug 139542






Comment 11


Mariano Suárez-Alvarez





          2004-04-18 02:33:07 UTC
        



*** Bug 139094 has been marked as a duplicate of this bug. ***






Comment 12


Mariano Suárez-Alvarez





          2004-04-20 14:55:25 UTC
        



*** Bug 140578 has been marked as a duplicate of this bug. ***






Comment 13


Mariano Suárez-Alvarez





          2004-04-29 17:36:07 UTC
        



*** Bug 141368 has been marked as a duplicate of this bug. ***






Comment 14


Mariano Suárez-Alvarez





          2004-05-12 18:46:18 UTC
        



*** Bug 142384 has been marked as a duplicate of this bug. ***