Bug#491461: vim-gtk: vim gtk exits with segfault

2008-08-25 Thread James Vega
reassign libxml2 2.6.32.dfsg-2+lenny1 forcemerge 496125 491461 thanks On Tue, Aug 26, 2008 at 02:38:34AM +0200, Mickael Wolff wrote: I tracked the bug. It raises when libxml 2.6.32.dfsg+lenny1 version is installed instead of 2.6.32.dfsg. Thanks for finding the problem, Mickael. Reassigning

Bug#491461: vim-gtk: vim gtk exits with segfault

2008-08-24 Thread Eike von Seggern
Package: vim-gtk Version: 2:7.2.000-2 Followup-For: Bug #491461 I have a similar problem as Hermann. The backtrace looks different but gvim is not usable. I've updated from vim 7.1 to version 7.2 in the hope, the segfault would disapear. Running in gdb yields: $ LANG=C gdb -q vim.gtk (gdb) set

Bug#491461: vim-gtk: vim gtk exits with segfault

2008-08-24 Thread James Vega
On Sun, Aug 24, 2008 at 02:32:54PM +0200, Eike von Seggern wrote: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb6f88950 (LWP 32194)] 0xb73d80a0 in ?? () from /lib/i686/cmov/libc.so.6 (gdb) bt #0 0xb73d80a0 in ?? () from /lib/i686/cmov/libc.so.6 #1 0x

Bug#491461: vim-gtk: vim gtk exits with segfault

2008-08-24 Thread James Vega
On Sun, Aug 24, 2008 at 03:28:25PM +0200, emil meier wrote: On Sun, Aug 24, 2008 at 08:52 -0400, James Vega wrote: Could you install vim-dbg so the backtrace is more useful? Also, could you attach the output of another run through strace (strace -o vim.log vim.gtk -g -u NONE -U NONE)?