2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce this are
complicated, and possibly very specific to the
On Sat, Dec 27, 2008 at 3:15 AM, Dominique Pelle wrote:
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce
On 27/12/08 09:46, Matt Wozniski wrote:
On Sat, Dec 27, 2008 at 3:15 AM, Dominique Pelle wrote:
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb.
On 27/12/08 04:43, Markus Heidelberg wrote:
björn, 26.12.2008:
Hi,
Currently if I use the mouse to close a tab (click the close button
on Mac, right-click tab and select close on pop-up menu on Windows)
when there is a modified buffer I get the following warning message:
E37: No write
You can compile your own Vim 7.2.075, see
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
I'm sure Matt is completely capable of doing this, Tony, and almost
certainly needs no assistance.
Before reporting a bug, it is always better to try reproducing it with
the latest
On 27/12/08 15:45, Ben Schmidt wrote:
You can compile your own Vim 7.2.075, see
http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
I'm sure Matt is completely capable of doing this, Tony, and almost
certainly needs no assistance.
Before reporting a bug, it is always better to try
Matt Wozniski wrote:
I tried to reproduce it but I could not.
Yeah, I'm not surprised... the fact that it seems tied to a hash
table resizing makes me think that it's very much tied to the number
of plugins I have loaded, the number of variables I have defined, and
a whole bunch of other,
This patch does not apply cleanly against the 7.2 extra tar.gz. The
code release has the following Id line:
* $Id: if_sniff.c,v 1.4 2006/03/06 23:13:51 vimboss Exp $
This makes downloading the source code releases and sequentially
applying the patches difficult to automate as hunk 1 of this
This patch does not apply cleanly due to the Id string. When building
using the 7.2 extra tar distribution (ftp://ftp.vim.org/pub/vim/extra/
vim-7.2-extra.tar.gz) the Id string is:
* $Id: if_sniff.c,v 1.4 2006/03/06 23:13:51 vimboss Exp $
which corresponds to 7.2.000.
It looks like the Id
