vim-gnome crashes

vim.tiny does work in the same situation.

ltrace shows this sequence leading up to the crash:

malloc(512) = 0x822f3e0
__strtol_internal("20,"50", NULL, 10) = 20
strlen("~/.gvimrc\n") = 10
malloc(11) = 0x822f380
memmove(0x822f380, 0x822e3fa, 11, 0x822e3fa, 0x822e290) = 0x822f380
strlen("~/.gvimrc") = 9
fwrite("\n> ", 1, 3, 0x822e290) = 3
_IO_putc('~', 0x822e290) = 126
_IO_putc('/', 0x822e290) = 47
_IO_putc('.', 0x822e290) = 46
_IO_putc('g', 0x822e290) = 103
_IO_putc('v', 0x822e290) = 118
_IO_putc('i', 0x822e290) = 105
_IO_putc('m', 0x822e290) = 109
_IO_putc('r', 0x822e290) = 114
_IO_putc('c', 0x822e290) = 99
_IO_putc('\n', 0x822e290) = 10
fgets("\t"\t32\t0\n", 512, 0x822e128) = 0x822e3f8
fputs("\t"\t32\t0\n", 0x822e290) = 1
fgets("\t"\t32\t0\n", 512, 0x822e128) = NULL
fclose(0x822e290) = 0
fclose(0x822e128) = 0
strcmp("/home/mbp/.viminfo.tmp", "/home/mbp/.viminfo") = 1
__xstat(3, "/home/mbp/.viminfo.tmp", 0xbff51664) = 0
unlink("/home/mbp/.viminfo") = 0
rename("/home/mbp/.viminfo.tmp", "/home/mbp/.viminfo") = 0
Py_IsInitialized(1, 6, 0xbff517d8, 0x80f3efb, 46) = 0
write(1, "Vim: Finished.\r\n\033[47;1H", 23Vim: Finished.
) = 23
sigset(11, 0, 0xbff517c8, 0x819be5b, 1) = 2
getpid() = 22481
kill(22481, 11 <unfinished ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
ltrace vim 0.27s user 1.38s system 78% cpu 2.115 total

vim.gtk does work too, so it seems to be specific to vim.gnome, even though it can be reproduced when run without X.

Thank you for your bug report. I have a few questions for you.

What version of the vim-gnome package is installed?

Does this crash also happen when you invoke it as "gvim"?

What happens if you run it as "vim -u NONE -U NONE"? Any change?

Does it still crash when you invoke it without a filename argument?

On 6/16/07, Micah Cowan <email address hidden> wrote:
> Thank you for your bug report. I have a few questions for you.
>
> What version of the vim-gnome package is installed?
>
> Does this crash also happen when you invoke it as "gvim"?
>
> What happens if you run it as "vim -u NONE -U NONE"? Any change?
>
> Does it still crash when you invoke it without a filename argument?

This is very annoying, but after removing and reinstalling the package
it is now working correctly.

The version was 1:7.0-164+1ubuntu7.1

The crash happened when run as vim, vi or gvim.

I didn't test -u and -U, but I did run it as a root, who has no vimrc or gvimrc.

It did crash whether there were filenames or not.

--
Martin

Actually, running as root will still use the default vimrcs in /etc, so it's not really equivalent.

Given that it is now working after an install, it doesn't appear that we'll have enough information to resolve whatever caused this problem. I'm going to close this bug report out, but please feel free to reopen it if you have any more information that would help track it down.