Ubuntu
vim package

SIGSEGV in setup_context for vim -g in karmic

Bug #510362 reported by Cory Dodt on 2010-01-20

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	vim (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: vim

Perfectly functioning gvim in jaunty. I upgraded to Karmic last night and this started happening today. This happens with any gvim invocation.

Expected: a gvim window to appear

Actual: crashes at the console before any window is drawn.
Vim: Caught deadly signal SEGV
Vim: Finished.
zsh: segmentation fault command vim -g

Additional notes:
- I can run -U /dev/null -u /dev/null and get the same results.

- vim, even vim.gnome invocation works fine/as expected with or without my startup files

(gdb) bt
#0 0x00007ffff5284165 in setup_context (message=0x7fffe915a7b0, category=0xd9aed0, stack_level=0) at ../Python/_warnings.c:467
#1 do_warn (message=0x7fffe915a7b0, category=0xd9aed0, stack_level=0) at ../Python/_warnings.c:611
#2 0x00007ffff528467b in PyErr_WarnEx (category=0xd9aed0, text=<value optimized out>, stack_level=1) at ../Python/_warnings.c:737
#3 0x00007fffe74be954 in ?? () from /usr/lib/pymodules/python2.6/gtk-2.0/gobject/_gobject.so
#4 0x00007ffff6bfaa89 in IA__g_logv (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>,
args1=0x7fffffffcd70) at /build/buildd/glib2.0-2.22.3/glib/gmessages.c:519
#5 0x00007ffff6bfaea3 in IA__g_log (log_domain=0x7fffe915a7b0 "\001", log_level=14266064, format=0x0)
at /build/buildd/glib2.0-2.22.3/glib/gmessages.c:569
#6 0x00007ffff64a3eb0 in gnome_program_preinit () from /usr/lib/libgnome-2.so.0
#7 0x00007ffff64a623c in ?? () from /usr/lib/libgnome-2.so.0
#8 0x00007ffff64a650d in gnome_program_initv () from /usr/lib/libgnome-2.so.0
#9 0x00007ffff64a660a in gnome_program_init () from /usr/lib/libgnome-2.so.0
#10 0x000000000059e309 in gui_mch_init () at gui_gtk_x11.c:3480
#11 0x0000000000592dbf in gui_init () at gui.c:457
#12 0x000000000057f6b9 in set_termname (term=0xb11348 "gui") at term.c:1845
#13 0x0000000000593389 in gui_start () at gui.c:91
#14 0x00000000004c9964 in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:635

cdodt 2 ~/wc/m1% apt-cache policy vim-gnome
vim-gnome:
  Installed: 2:7.2.245-2ubuntu2
  Candidate: 2:7.2.245-2ubuntu2
  Version table:
*** 2:7.2.245-2ubuntu2 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Revision history for this message

Cory Dodt (corydodt) wrote on 2010-01-20:

vim.gtk -g does *not* crash. Somehow this is vim.gnome-specific.

Revision history for this message

Cory Dodt (corydodt) wrote on 2010-01-20:

vimchat.vim.disabled Edit (56.4 KiB, text/plain)

jamessan set me straight on how to use -U -u properly so here's an update:

vim.gnome -g -U NONE -u NONE *does* in fact start up a gvim window. vim.gnome -g --noplugin also starts up successfully.

Further investigation revealed that the attached plugin is the culprit. I'm mildly curious why the crash occurs, but I can safely say that I don't need this and it's unreleased code anyway.

For completeness, reportbug output:

Package: vim-gnome
Version: 2:7.2.245-2ubuntu2
Severity: wishlist

-- System Information:
Debian Release: squeeze/sid
APT prefers karmic-updates
APT policy: (500, 'karmic-updates'), (500, 'karmic-security'), (500, 'karmic-backports'), (500, 'karmic')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-17-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-gnome ii libacl1 2.2.47-2 ii libbonoboui2-0 2.24.2-1ubuntu2 ii libc6 2.10.1-0ubuntu16 ii libglib2.0-0 2.22.3-0ubuntu1 ii libgnome2-0 2.28.0-0ubuntu3 ii libgnomeui-0 2.24.2-1 ii libgpm2 1.20.4-3.2ubuntu1 ii libgtk2.0-0 2.18.3-1ubuntu2.1 ii libice6 2:1.0.5-1 ii libncurses5 5.7+20090803- Access control list shared library
The Bonobo UI library
GNU C Library: Shared libraries
The GLib library of C routines
The GNOME library - runtime files
The GNOME libraries (User Interfac
General Purpose Mouse - shared lib
The GTK+ graphical user interface
X11 Inter-Client Exchange library
/>2ubuntu2 shared libraries for terminal hand
Layout and rendering of internatio
Shared Perl library
Shared Python runtime library (ver
Libraries necessary to run Ruby 1.
SELinux shared libraries
X11 Session Management library
X11 client-side library
X11 toolkit intrinsics library
Tcl (the Tool Command Language) v8
Vi IMproved - Common files
Vi IMproved - Common GUI files
Vi IMproved - Runtime files

vim-gnome recommends no packages.

Versions of packages vim-gnome suggests:
pn cscope <none> (no description available)
ii gnome-icon-theme 2.28.0-0ubuntu1 GNOME Desktop icon theme
ii ttf-dejavu 2.29-2 Metapackage to pull in ttf-dejavu-
pn vim-doc <none> (no description available)

-- no debconf information

jamessan set me straight on how to use -U -u properly so here's an update:

vim.gnome -g -U NONE -u NONE *does* in fact start up a gvim window.  vim.gnome -g --noplugin also starts up successfully.

Further investigation revealed that the attached plugin is the culprit.  I'm mildly curious why the crash occurs, but I can safely say that I don't need this and it's unreleased code anyway.

For completeness, reportbug output:

Package: vim-gnome
Version: 2:7.2.245-2ubuntu2
Severity: wishlist

-- System Information:
Debian Release: squeeze/sid
  APT prefers karmic-updates
  APT policy: (500, 'karmic-updates'), (500, 'karmic-security'), (500, 'karmic-backports'), (500, 'karmic')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-17-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vim-gnome depends on:
ii  libacl1            2.2.47-2              Access control list shared library
ii  libbonoboui2-0     2.24.2-1ubuntu2       The Bonobo UI library
ii  libc6              2.10.1-0ubuntu16      GNU C Library: Shared libraries
ii  libglib2.0-0       2.22.3-0ubuntu1       The GLib library of C routines
ii  libgnome2-0        2.28.0-0ubuntu3       The GNOME library - runtime files
ii  libgnomeui-0       2.24.2-1              The GNOME libraries (User Interfac
ii  libgpm2            1.20.4-3.2ubuntu1     General Purpose Mouse - shared lib
ii  libgtk2.0-0        2.18.3-1ubuntu2.1     The GTK+ graphical user interface
ii  libice6            2:1.0.5-1             X11 Inter-Client Exchange library
ii  libncurses5        5.7+20090803-2ubuntu2 shared libraries for terminal hand
ii  libpango1.0-0      1.26.0-1              Layout and rendering of internatio
ii  libperl5.10        5.10.0-24ubuntu4      Shared Perl library
ii  libpython2.6       2.6.4-0ubuntu3        Shared Python runtime library (ver
ii  libruby1.8         1.8.7.174-1ubuntu1    Libraries necessary to run Ruby 1.
ii  libselinux1        2.0.85-2ubuntu2       SELinux shared libraries
ii  libsm6             2:1.1.0-2             X11 Session Management library
ii  libx11-6           2:1.2.2-1ubuntu1      X11 client-side library
ii  libxt6             1:1.0.5-3ubuntu1      X11 toolkit intrinsics library
ii  tcl8.4             8.4.19-3              Tcl (the Tool Command Language) v8
ii  vim-common         2:7.2.245-2ubuntu2    Vi IMproved - Common files
ii  vim-gui-common     2:7.2.245-2ubuntu2    Vi IMproved - Common GUI files
ii  vim-runtime        2:7.2.245-2ubuntu2    Vi IMproved - Runtime files

vim-gnome recommends no packages.

Versions of packages vim-gnome suggests:
pn  cscope                   <none>          (no description available)
ii  gnome-icon-theme         2.28.0-0ubuntu1 GNOME Desktop icon theme
ii  ttf-dejavu               2.29-2          Metapackage to pull in ttf-dejavu-
pn  vim-doc                  <none>          (no description available)

-- no debconf information

Revision history for this message

Dominique Pellé (dominique-pelle) wrote on 2010-02-11:

I can't reproduce this bug. Vim or gVim (built with Python)
do not crash for me when putting vimchat.vim in my ~/.vim/plugin
directory.

However:

- I have not spent time figuring out how this plugin works. Perhaps
you have some settings in your ~/.vimrc which trigger the bug.
If you don't mind, can you send your ~/.vimrc file?

- when starting Vim (built with Python interpreter) with valgrind
  memory checker, I see some accesses to freed memory (see
  http://dominique.pelle.free.fr/valgrind-errors-vim7.2.351-python2.6.4.txt)
  even without the plugin. I don't know yet whether this bug
  in the Python lib or in Vim. See this thread in vim_dev mailing
  list:
  http://groups.google.com/group/vim_dev/browse_thread/thread/11ed0e435190ccb