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 137826 - glib 2.4.0 cause gnome-terminal crash when starting vim in it.
glib 2.4.0 cause gnome-terminal crash when starting vim in it.
Status: RESOLVED DUPLICATE of bug 139542
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-21 03:29 UTC by suzhe
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description suzhe 2004-03-21 03:29:38 UTC 
Distribution: TurboLinux Turbolinux Desktop 10.0 (Suzuka)
Package: gnome-terminal
Severity: normal
Version: GNOME2.4.1 2.4.1
Gnome-Distributor: GNOME.Org
Synopsis: glib 2.4.0 cause gnome-terminal crash when starting vim in it.
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.4.1
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

After I upgraded to glib 2.4.0, gnome-terminal always crashed each time
when I run vim in it. The locale was zh_CN.GB18030. And the error
message was:

** (gnome-terminal:3224): 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塣

(process:3224): GLib-CRITICAL (recursed) **: file gstring.c: line 672
(g_string_erase): assertion `pos >= 0' failed
aborting...

Steps to reproduce the crash:
1. start gnome-terminal
2. run vim
3. 

Expected Results:


How often does this happen?

every time.

Additional Information:



Debugging Information:

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

(no debugging symbols found)...[New Thread 16384 (LWP 3224)]
0x404f9e48 in waitpid ()
   from /lib/libpthread.so.0

+ Trace 45316

Thread 1 (Thread 16384 (LWP 3224))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 valid
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    at sighandler.c line 38
  • #3 <signal handler called>
  • #4 kill
    from /lib/libc.so.6
  • #5 pthread_kill
    at signals.c line 65
  • #6 __pthread_raise
    at signals.c line 187
  • #7 raise
    at ../linuxthreads/sysdeps/unix/sysv/linux/raise.c line 34
  • #8 abort
    at ../sysdeps/generic/abort.c line 88
  • #9 g_logv
  • #10 g_log
  • #11 g_string_erase
    at gstring.c line 682
  • #12 escape_string
    at gmessages.c line 795
  • #13 g_log_default_handler
    at gmessages.c line 888
  • #14 g_logv
    at gmessages.c line 503
  • #15 g_log
    at gmessages.c line 541
  • #16 vte_terminal_handle_sequence
    at vte.c line 6659
  • #17 vte_terminal_process_incoming
    at vte.c line 7112
  • #18 g_timeout_dispatch
    at gmain.c line 3250
  • #19 g_main_dispatch
    at gmain.c line 1895
  • #20 g_main_context_dispatch
    at gmain.c line 2441
  • #21 g_main_context_iterate
    at gmain.c line 2522
  • #22 g_main_loop_run
    at gmain.c line 2726
  • #23 gtk_main
    at gtkmain.c line 1093
  • #24 main
  • #25 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 225
  • #0 waitpid
    from /lib/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-20 22:29 -------

Unknown version 2.4.1 in product gnome-terminal. Setting version to the default, "unspecified".
The original reporter (suzhe@tsinghua.org.cn) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.
Comment 1 Mariano Suárez-Alvarez 2004-04-18 02:02:26 UTC 
This is caused by bug 139542 through 139441.

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